Layer.Yahoo and Layer.WFS don't play well together

[elemoine]

Carole Zieler reported an error with a map using a Yahoo layer and a WFS layer. The error is:

position has no properties
this.position = position.clone();

It occurs on every moveTo to the WFS layer.

Based on code she gave me I could write a stripped down example and reproduce the problem. See carole.html.

I have no idea what the problem is. I could just find out that the cause of the problem is the Yahoo convertLatLonXY func (called in Layer.Yahoo::getMapObjectPixelFromMapObjectLonLat) returning false instead of a pixel object.

[crschmidt]

Yahoo's API doesn't let you get a latlon from a pixel when the pixel is outside the viewport area -- this might be the problem, if you dragged the map far enough that it was outside the viewport area or something?

Just a comment/guess, no real investigatoin on my part.

[elemoine]

crschmidt, the problem doesn't occur in a pixel-to-lonlat conversion but in lonlat-to-pixel conversion (convertLatLonXY).

[crschmidt]

Elemoine:

Give this a try and see if it helps. Sine we never use the pos of WFS tiles (it's largely meaningless) I think we can just fake it, and drop the call that fails from the WFS layer.

(This will all go away with vector behavior, of course.)

[euzuro]

Unclear exactly what I am supposed to do/see in carole.html related to this bug, but I do get script errors, even with this patch applied.

Unless someone is dying for this to get in, it's going to 2.8

[crschmidt]

So, I've just tried this example, and tried to reproduce the underlying problem. I definitely had something I could reproduce before, and now I can't -- I believe this is because Yahoo!'s API changed. (That's nice, since I've only been asking for that for a long time.) So, I think that Yahoo!'s API updates have made this no longer valid.