On 11/08/2012 07:19 PM, Bobby Holley wrote:
The current spec for the Location object doesn't match reality. At the
moment, the spec says that Location is a per-Window object that describes
the associated Document. However, in our testing, it appears that none of
the user-agents (Gecko, WebKit,
Merci beaucoup Pierre. That was quite a detailed reply!
--
Nicholas.
On Thu, Nov 8, 2012 at 10:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 11/8/12 6:09 PM, Adam Barth wrote:
I don't think I quite understand what you mean, but the way this works
in WebKit is that each Window object has its own Location object.
That's not how it works in Presto and Trident,
On Fri, Nov 9, 2012 at 9:30 AM, Adam Barth w...@adambarth.com wrote:
On Thu, Nov 8, 2012 at 10:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
You presumably have a solution for this situation for the WindowProxy
case,
right? Certainly Gecko does, and we would be using the same solution for
On 2012-11-07 23:41, Ian Hickson wrote:
On Thu, 8 Nov 2012, Ben Schwarz wrote:
What does concern me, as a web builder, *every day*, is how I markup the
content in-between a header and a footer.
If you just want it for styling purposes, div is perfect.
article
headerh1, h2, p/header
div
On 2012-11-08 10:51, Steve Faulkner wrote:
What the relevant new data clearly indicates is that in approx 80% of cases
when authors identify the main area of content it is the part of the
content that does not include header, footer or navigation content.
It also indicates that where skip
Starting a new subject on this to keep the email threads more clear:
Suggestion is that the following should be possible,
this would allow body to act as if it was a main.
!doctype html
html
head
titleheader and footer outside body/title
style
body {border:1em solid #7f2424;}
header {border:1em
On Fri, Nov 9, 2012 at 12:06 PM, Bobby Holley bobbyhol...@gmail.com wrote:
On Fri, Nov 9, 2012 at 11:33 AM, Adam Barth w...@adambarth.com wrote:
That was my opinion for a while, too, but I eventually decided it was
necessary in Gecko.
Can you explain why you think it is necessary? In
On Fri, Nov 9, 2012 at 9:43 AM, Bobby Holley bobbyhol...@gmail.com wrote:
On Fri, Nov 9, 2012 at 9:30 AM, Adam Barth w...@adambarth.com wrote:
On Thu, Nov 8, 2012 at 10:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
You presumably have a solution for this situation for the WindowProxy
case,
On Fri, Nov 9, 2012 at 11:33 AM, Adam Barth w...@adambarth.com wrote:
That was my opinion for a while, too, but I eventually decided it was
necessary in Gecko.
Can you explain why you think it is necessary? In WebKit, the
WindowProxy is the only object that has this magic.
As noted, the
On Fri, Nov 9, 2012 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
I don't think the average web developer will hit this case because it
depends on interacting with the Location object in an inactive
document.
Agreed.
Maybe I didn't receive your email.
Here's a link to it in the
On Fri, Nov 9, 2012 at 12:26 PM, Bobby Holley bobbyhol...@gmail.com wrote:
On Fri, Nov 9, 2012 at 12:17 PM, Adam Barth w...@adambarth.com wrote:
I don't think the average web developer will hit this case because it
depends on interacting with the Location object in an inactive
document.
On 11/9/12 2:05 PM, Adam Barth wrote:
The approach we use in WebKit is quite simple---we just perform an
access check before doing any sensitive operations.
The issue in Gecko, as I understand, is that security checks from C++
code require introspecting running JS to figure out what the
On Tue Nov 6 11:25:21 PST 2012, Ian Hickson wrote:
[snip]
This is a very interesting idea.
Is this something browser vendors would be interested in implementing? I'm
hesitant to add a feature for this (which could be somewhat involved)
before having the definite interest of some browser
14 matches
Mail list logo