two thoughts on tiling

Two things that I just thought of that I'm just writing here to avoid 
forgetting them.

1. One of the advantages of doing the tiling & layering natively in the 
browser was that the browser is in a better position to decide when to 
throw away cached tiles, since it could know more about the memory 
pressure.  I wonder if that could be generalised so that script could 
register some object (maybe a DOM object, maybe a JS object, maybe a 
blob URI) that the browser would be free to throw away, with events 
thrown when the object is thrown away so the script could know about that.

2. Let's assume we use <iframe> for the tiles.  Currently, <iframe>s 
capture all mouse events in the rectangle they cover, and part of the 
reason they do that is that if you have content from other origins 
inside the <iframe> you could possibly find out what the content is by 
testing pointer events over each pixel.  If you had tiles for, say, post 
office locations then you wouldn't want to capture mouse events over 
areas where the post office icons aren't.  How do we resolve this?

Received on Wednesday, 12 September 2012 15:13:18 UTC