if you could extend
this trust to the Webtop by guaranteeing that it's the top-most
authority, then just like the browser the Webtop could have access to
every children's history. So I guess the top-down/bottom-up symmetry
is not so symmetric after all!
Anyways, thanks for clearing this out!
Kind regards,
Nick
>> By bookmark, I mean the Webtop being able to read the current location
>> of the website and saving that to the server-side. By save a session,
>> I mean the Webtop being able to read the location of all iframes it
>> created and saving that to the server-side for later retrieval.
>
> Reading th
10 at 1:42 PM, Adam Barth wrote:
> What do you mean by access to the iframe's browsing context? Is that
> access you would have if the iframe were not sandboxed?
>
> Adam
>
>
> On Mon, Sep 6, 2010 at 7:31 AM, Nick Vidal wrote:
>> In addition to allow-top-navigatio
the parent document would have
access only to the browsing context of the iframe. No other access
would be granted.
Best regards,
Nick
Notes:
1) More information here: http://itop.iss.im/
2) As previously discussed here:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027884.html
Op 24-7-2010 2:02, David Flanagan schreef:
Nick wrote:
Nice, less math.
I think the outside alignment approach will only work on paths that
have a 100% opacity fill.
You'r right.
The off-screen rectangle approach could work with opacity but it has
the same problem with transparent p
once it curves.
It would be nice if Canvas took care of stroke alignment so we can get
rid of the hacks and limitations those bring along.
--
Nick
Op 20-7-2010 19:36, David Flanagan schreef:
Nick wrote:
Canvas would benefit from a way to set stroke alignment. With the
only available alig
path once a path goes diagonal or curves.
Having Canvas take care of stroke alignment (center, inside and outside)
by adding something like strokeAlign can fix these transparency problems
and makes adding strokes a lot easier and more useful.
--
Nick Stakenburg
