Perhaps we want an allow-frame-busting directive? In the
implementation we have an allow-navigation bit that covers
navigation |top| as well as window.open, etc. Maybe we want a more
general directive that twiddles this bit?
I'm wondering if sites want to have control over the type of
On Sat, Feb 13, 2010 at 12:08 AM, Michal Zalewski lcam...@coredump.cx wrote:
Perhaps we want an allow-frame-busting directive? In the
implementation we have an allow-navigation bit that covers
navigation |top| as well as window.open, etc. Maybe we want a more
general directive that twiddles
On Feb 12, 2010, at 11:54 PM, Adam Barth wrote:
On Fri, Feb 12, 2010 at 11:48 PM, Michal Zalewski
lcam...@coredump.cx wrote:
Can a frame in @sandbox ever navigation the top-level frame? If
not,
that would make it hard to use @sandbox to contain advertisements,
which want to navigate |top|
Maciej Stachowiak schrieb:
On Feb 12, 2010, at 11:54 PM, Adam Barth wrote:
On Fri, Feb 12, 2010 at 11:48 PM, Michal Zalewski
lcam...@coredump.cx wrote:
Can a frame in @sandbox ever navigation the top-level frame? If not,
that would make it hard to use @sandbox to contain advertisements,
I don't know... to me, asynchronous means completes later. Precedence:
XMLHttpRequest.
The Mozilla network code uses the phrase load background to describe a
load that happens asynchronously in the background _and_ does not block
onload. Perhaps not coincidentally, this mode is used to load
The thing is, almost all subresources load asynchronously. The load event
exists to tell us when those asynchronous loads have finished. So, I think
it follows that an asynchronous resource load may reasonably block the load
event. (That's the point of the load event afterall!)
-Darin
On
Hi,
as Ilmari pointed out in his letter some.. hmm.. time ago [1] Canvas spec
is missed method isPointInStroke(). It is _important_ thing as this
will be used for generating dynamic charts and graphs. For the moment,
selecting some point on a curve is not trivial problem...
(Although my real
On 2/13/10 9:29 AM, Darin Fisher wrote:
The Mozilla network code uses the phrase load background to describe a
load that happens asynchronously in the background _and_ does not block
onload. Perhaps not coincidentally, this mode is used to load
background images :-)
It used to be. It's not
FWIW, loading scripts asynchronously with the Script DOM Element approach
does not block window.onload in IE. In Chrome and Safari, the downloading
blocks, but execution doesn't. In Firefox and Opera, downloading and
execution blocks.
So, it's pretty hard to say what web developers would expect
On 2/12/10 9:23 AM, Tab Atkins Jr. wrote:
On Thu, Feb 11, 2010 at 9:29 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
Do you know of any actual authors who would want to use
validationMessage? If there are any authors here who would want to
use the validation API with their own UI, would
Section 9.2.3, step 5 reads:
Create an event that uses the MessageEvent interface, with the event name
message, which does not bubble, is not cancelable, and has no default action.
The data attribute must be set to the value of message clone, the origin
attribute must be set to the Unicode
On Sat, Feb 13, 2010 at 12:52 PM, Brian Kuhn bnk...@gmail.com wrote:
FWIW, loading scripts asynchronously with the Script DOM Element approach
does not block window.onload in IE. In Chrome and Safari, the downloading
blocks, but execution doesn't. In Firefox and Opera, downloading and
I agree with Erik. It's useful if the pseudo classes work without a form
element and name attribute. input element is often used without a form
element in web applications.
A related topic:
13 matches
Mail list logo
