On Thu, Sep 15, 2011 at 9:55 AM, Ian Hickson i...@hixie.ch wrote:
[...]
However, as easy as that appears at first blush, I fear it would be seem
quite magical to authors who have trouble enough understanding CSS as it
is. Consider:
aside
section
style scoped
aside section
Fair dames and damsels of the list
Consider
http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element:
The summary element represents a summary, caption, or legend for the rest
of the contents of the summary element's parent details element,
On Tue, 20 Sep 2011, Bruce Lawson wrote:
Fair dames and damsels of the list
Consider
http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-summary-element:
The summary element represents a summary, caption, or legend for the rest of
the contents of the
We're implementing window.onerror in Opera. In order to not expose the URL
of redirects in cross-origin resources with window.onerror, errors from
cross-origin scripts are masked in Gecko and WebKit, i.e. instead of
invoking window.onerror with a useful error message, a URL and the line
* Simon Pieters wrote:
This makes window.onerror rather useless for cross-origin scripts.
However, it is still possible to tell if the user is logged in or not if a
site serves a script for a particular URL when the user is logged in and
redirects to the home page or so when the user is not
I am reading:
Contexts in which this element can be used:
As the first child of a
detailshttp://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#the-details-elementelement.
My feeling is that unconnected DOM elements in a script are not really an
HTML document but
I had a discussion with Jonas on IRC and we've come to a conclusion that we
should have both boolean argument and reapply.
The rationale is that if apply/reapply share most code and only requires
some work before/after the shared code, then reapply can simply call apply
inside. On the other hand
On 9/20/11 5:40 PM, Simon Pieters wrote:
However, it is still possible to tell if the user is logged in or not if
a site serves a script for a particular URL when the user is logged in
and redirects to the home page or so when the user is not logged in.
Can't you tell this from the load event
