to resolve URLs in the same way as
> XMLHttpRequest. Does "first script" really make sense here? I also
> wonder if "first script" is actually ever used for this. (Did not put
> time in investigating that for now.)
This should be fixed in the browsers, IMHO.
his is indeed the kind of thing which CSP might fix in the medium-term
future. If it turns out that CSP, or whatever CSP gets replaced by,
doesn't solve this use case, then we should revisit it.
Cheers,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Thu, 9 Sep 2010, Henri Sivonen wrote:
> On Sep 9, 2010, at 00:47, Ian Hickson wrote:
> > On Fri, 3 Sep 2010, Henri Sivonen wrote:
> >>
> >> When evaluating a parser-inserted script, there are three potential
> >> script global objects to use:
> >
ndow.btoa():
>
> http://aryeh.name/spec/base64.html
>
> These are functions supported by all browsers except IE, which do base64
> encoding and decoding.
Awesome. I've updated the spec accordingly.
> I also wrote a fairly complete test suite, at:
> http://dvcs.w3.org
On Mon, 31 Jan 2011, Glenn Maynard wrote:
> On Mon, Jan 31, 2011 at 7:12 PM, Ian Hickson wrote:
> >
> > Given that SxS manifests don't seem like they'd ever be something
> > you'd want to make available to download standalone, and that if you
> > were g
in entries
> would be skipped (matching today's behavior).
I'm not a fan of hardcoded URLs, as they fail in a number of scenarios
(e.g. a server shared by different teams that trust each other but may
have different needs).
Before we discuss solutions, though, we should be clear what problem we're
trying to solve. What is the security risk you are looking to mitigate?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Mon, 31 Jan 2011, Glenn Maynard wrote:
> On Mon, Jan 31, 2011 at 6:46 PM, Ian Hickson wrote:
>
> > > That's far too generic for servers to default to mapping *.manifest
> > > to text/cache-manifest. For example, Windows uses *.manifest for
> > > SxS as
On Mon, 31 Jan 2011, Glenn Maynard wrote:
> On Mon, Jan 31, 2011 at 6:28 PM, Ian Hickson wrote:
> > On Fri, 13 Aug 2010, David John Burrowes wrote:
> > >
> > > I can understand wanting to do things right, in terms of using
> > > Content-Type for the file.
oth cases, there would also be an associated navigator API:
>
> void navigator.installApplication();
> bool navigator.isInstalled;
I don't think that makes any sense. It's the Web. There's no
"installation" step. You just run the app. There's nothing to
On Fri, 13 Aug 2010, Patrick Mueller wrote:
> On 8/12/10 6:29 PM, Ian Hickson wrote:
> > On Thu, 29 Jul 2010, Anne van Kesteren wrote:
> > >
> > > XML would be much too complex for what is needed. We could possibly
> > > remove the media type check and
the outer level one does not.)
>
> Browser implementations allow primitives such as strings to be passed to
> History.pushState(), window.postMessage() and other methods that
> reference the structured clone algorithm.
>
> I think you can fix this by changing "object" to
all, that's not currently meant to be allowed.
This is intended to be up to the user. We should clarify this in the File
API specs, though.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
n, e.g. Web Workers,
Server-Sent Events, +, etc.)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
or a professor, possibly via e-mail. That's why I'd like
> to have localStorage implemented in an e-mail compatible fashion.
> Hopefully, the localStorage implementation would also be compatible with
> dropboxes.
It's not clear to me what you're aski
g as the behaviour is
consistent, e.g. that the boundaries used for text-transform:capitalize
match the boundaries used for word boundaries in Selection.modify(). This
may need some coordination work so that the specs use terminology that is
unambiguously referring to equivalent concepts, with
up,
the WHATWG one is now a superset of the W3C one, but is still just "HTML"
things and not anything Web related.
There's a separate WHATWG spec that contains everything still, including
the HTML stuff and stuff like Web Storage:
http://www.whatwg.org/specs/web-apps/cur
k a part of your page is "a section with navigation
links", then you can use (but you aren't required to).
For authors who have been writing HTML pages for a while, another way of
putting it is "use whenever you would have used
before". So long as you used class="
s of a site, such as the terms of service,
> the home page, and a copyright page. The footer element alone is
> sufficient for such cases, without a nav element."
It doesn't say it's inappropriate, such that it's not necessary. It's
still fine to use it
e). However, what's the use case for the
page writing its own IME from scratch?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
menting the CSS 'unicode-bidi' property.
> > + [CSS]
>
> s/should/could/
Thanks. Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
k/complete/introduction.html#conformance-requirements-for-authors
Indeed.
On Tue, 9 Nov 2010, Silvia Pfeiffer wrote:
>
> As long as the percent-values aren't deprecated... cause if they are, IE
> behavior would be accurate, IMO.
They're more than deprecated, they'
ssue to consider here is what happens when the machine goes to
> sleep, and then wakes up. This is a much more common scenario than the
> user changing the system clock.
The spec seems to handle this case (the timers aren't stopped by the
system being suspended, but e.g. setIn
son that would make the current behavior
> more appropriate than the one described here.
In the end I'll spec whatever gets implemented. What do other browser
vendors feel about this? Should we make required="" on any one type=radio
control affect the val
On Tue, 2 Nov 2010, Charles Pritchard wrote:
> On 11/1/2010 6:03 PM, Ian Hickson wrote:
> > On Thu, 26 Aug 2010, Charles Pritchard wrote:
> > > On 8/25/2010 2:02 PM, Ian Hickson wrote:
> > > > On Mon, 2 Aug 2010, Charles Pritchard wrote:
> > > > > >
On Thu, 6 Jan 2011, Glenn Maynard wrote:
> On Thu, Jan 6, 2011 at 8:10 PM, Ian Hickson wrote:
> > * Helping authors not write HTML markup that might be hard to convert to
> > XML, and helping authors avoid nesting comments accidentally, by
> > flagging "
ther more useful, but then I use "--" as long
dashes all the time! When this was last studied, the weight of argument
was on the stricter "disallow --" side of things, presumably.
I'm open to changing this back; does anyone else have an opinion on this?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
, the question of optimizing the "color picker"
> interface so that a human can choose "precisely" (modulo psy) a
> predetermined color (in RGB, HSV, or CIELAB space) in the least amount
> of time, has not, I would claim, yet been optimized. I think the optimal
> solution would involve throttles in an intrinsically toroidal space.
This is the kind of experimentation I hope we will see in browsers with
things like type=number.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Thu, 28 Oct 2010, Andrew Oakley wrote:
>
> Is there any reason that the PageTransitionEvent persisted attribute
> (and corresponding argument to initPageTransitionEvent) is of type any
> rather than boolean?
Copypasta. Fixed.
--
Ian Hickson
to be a single line in the rendering, and so allowing
elements that are intentionally separate "blocks" sends the wrong message.
It would also be rather weird to have what is intended to be a disclosure
widget be its own "section" in the document outline.
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
.
What are the use cases for this feature?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Wed, 27 Oct 2010, Diogo Resende wrote:
>
> Is there a way to know that a has been loaded (and processed)?
> I'm more interested in CSS links than others but the process should be
> the same. In my opinion it's a better way of loading stylesheets than
> downloading using XmlHttpRequest and t
ble names that aren't too verbose.)
This is defined in the part of the spec starting with "When the multiple
attribute is specified on the element".
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Fri, Oct 22, 2010 at 7:13 PM, Anne van Kesteren wrote:
> > Sure, I would expect the way it is serialized for submission and for
> > .value to be the same. I would not expect any whitespace there either.
> > The way it is currently defined does not make much sense to me and
> > seems to assume a particular UI.
>
> I filed a bug:
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11137
Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
font styles,
leaving that up to the default binding.)
We can change the spec here if there's a reason to do so, but as you say,
I'd be surprised if there were interop needs here, so the simplest
behaviour (nothing special) seems the best.
--
Ian Hickson U+1047E
e an
> app that gave you a 1 minute warning on the need for an umbrella.
>
> I am not going to pass any judgement on how hip this would be, but those
> are the uses I can see.
I think we're some way away from having many users run background Web apps
on the
a DOMString for most
purposes, but to allow methods to be invoked on it. (All the attributes
that have [PutForwards] set also have a stringifier on their object's
interface.)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A
e '\r' characters)?
Yes.
> If so, does that mean that setSelectionRange() should operate on the
> raw, internal value (that just has '\n' for newlines in it normally),
> but the 'value' getter still returns the transformed value with newlines
> normalized
On Wed, 6 Oct 2010, Narendra Sisodiya wrote:
>
> I think, web developed should be done modular design approach.
This is more or less what XBL is intended to do:
http://dev.w3.org/cvsweb/~checkout~/2006/xbl2/Overview.html?content-type=text/html;%20charset=utf-8
--
Ian H
is applied to each individual component of the value,
> rather than the value as a whole.
Done.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
et up a redirect but I flubbed the syntax and forgot
to check it. Fixed. Thanks.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
vigate"
algorithm for details on what happens when a page loads, including when a
new Window object is created:
http://www.whatwg.org/specs/web-apps/current-work/complete.html#navigate
Note in particular the exception listed under "creating a new Document
object", which may be
appear to be the end of the start tag but that do not
intend to have the browser close the element immediately.
For example, markup such as the following is sadly common:
Hello world!
I have therefore not changed the spec in response to this request.
--
Ian Hickson U+1047
a 100-character string in one
browser it actually takes just 100 bytes, but on another browser it might
take 1000. So not only would the information be unreliable, it would be
insufficient to really make good judgements.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
without any possible action from the user.
>
> If there is no specific use cases in mind I think we should just remove
> that.
It's so that you can use a in the (with the same
s) for fallback in older UAs, without that having any
effect on the form submission.
--
27;s onBlur -> OL's onFocus;
> - In Firefox (can't remeber version), the only event triggered is LI's
> onFocus;
I don't really know what it would mean to focus the elements if the
was already focused, really. I mean, everything that's editable has
to
e marked
> invalid but that might change before the final release if there is an
> agreement that :-moz-submit-invalid is a better way to fulfill the need.
>
> As a side note for web authors on this list, :-moz-submit-invalid
> currently has a default style on Firefox but th
hey will be presented with data that's already entered by someone else
> and their job is to clean up the data. In fact I see the new Form API to
> be a very good candidate for this use case.
Indeed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
st -- for this kind of thing
we'd probably want to use a direct API, we wouldn't want to have scripts
have to poke at the DOM in real time.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
t use timeouts to
test whether the worker started -- that way you'll do the worker-less
fallback behaviour regardless of whether the timeout fired because workers
are just slow on the user's computer or because there are no more worker
slots available.
--
Ian Hickson
t now incorrect) spelling, spelling
> intentionally done wrong for better rhyming (yes, people did this in the
> past) and unintentional errors from the book semantically. I think it is
> important to note where those errors are done intentional (by me,
e.g. if the
user printed the page, you'd want to provide data in the printer's native
resolution rather than the screen's. That's something that you'd want to
do regardless of JS being enabled or not, so it can't be a scripting API
-- it has to be an
d in terms of validity rather than in terms of successful
parsing, and added a paragraph and example clarifying this, along with
cross-references to this paragraph where relevant.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 21 Sep 2010, Jonas Sicking wrote:
>
> [list=""/ should show invalid values.] Consider for example:
>
>
>
>
>
>
Good use case. Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.
lso, it would mean that the following two pieces of code behaves differently:
>
> inp = document.createElement("input");
> inp.setAttribute("value", "foo\nbar");
> inp.setAttribute("type", "hidden");
>
> and
>
> in
ing a non-normative paragraph
> explaining the edge case would be nice. Otherwise, making the
> specification more clear would be required.
The paragraph you quote _is_ the non-normative paragraph. :-)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ow support particular event.
> Or what are the alternate events available, so that we can refer some
> document or do some test to find how it can be used.
> So I wish we had above methods available.
What do you mean by "supports an event"? You can dispatch any event y
;invalid" event implement an
> interface with a function like setCustomErrorMessage(in DOMString
> message). This string would then be displayed by the UA in its UI
> wherever it displays validation error messages.
>
> I actually think that the customerrormessage attribute that
ines of code here.
> I don't expect anything frankly, I only hope :). But I'm not hoping for
> priority of implementations, but rather that it be added to the spec.
Adding it to the spec doesn't do anything if it doesn't get added to
imple
kool' graphics where
> pixellation is actually desired, not smoothing.
It's on the list of things to look at in future versions. In the meantime,
browsers are experimenting in this area.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Sat, 11 Dec 2010, Bjartur Thorlacius wrote:
>
> How does HTML 5 relate to ECMAScript
HTML and JavaScript are both actively-maintained Web technologies.
> how does conformance with ECMA262 affect conformance with HTML 5?
It doesn't particularly.
HTH,
--
Ian Hickson
omatic features browsing context flag set when the
> Document was created".
Yeah, this was not quite what the change was meant to be. Fixed to go back
to the earlier behaviour, with the new restriction more appropriately
phrased.
--
Ian Hickson U+1047E)\._.,--.
leave timeupdate as it is, and fix
> > this in the future?
>
> I think so. Another factor is that a lot of the video effects people
> have been using canvas for can actually be done with SVG filters, which
> can be GPU-accelerated and are compatible with asynchronous compositin
does not replace
> a currently playing resource with a new one without glitches. When you load
> a new resource, you set the currentSrc to a new resource URL, then call
> load() and it will reset the player controls to start at the beginning, it
> will reset the currentTime to 0 and basical
uld fire an 'emptied' event for each that
> changed, which is kind of undesirable. Maybe the media element load
> algorithm should only be invoked if src is set or changed on a
> that has no previous sibling elements?
What's the use case? Just set .src before you insert t
would be appropriate for that spec. In case it is helpful to Anne,
I've included below the feedback to which I did not include responses.)
On Fri, 20 Aug 2010, Mike Wilcox wrote:
> On Aug 20, 2010, at 3:24 PM, Ian Hickson wrote:
> > By CSSOM, I mean a separate specification, specif
ge of opinions regarding what the right behaviour is,
implementations are still changing, and implementors often disagree with
their own implementations at this stage.
On Tue, 31 Aug 2010, Boris Zbarsky wrote:
> On 8/31/10 3:36 AM, Ian Hickson wrote:
> > > You might say "Hey, but aren&
On Wed, 18 Aug 2010, Silvia Pfeiffer wrote:
> On Wed, Aug 18, 2010 at 11:13 AM, Ian Hickson wrote:
> >
> > Agreed. I've made the API clearly say that "duration" is the time at
> > the end, even in the case where the start is not actually zero, to
> >
On Tue, 3 Aug 2010, Boris Zbarsky wrote:
> On 8/2/10 5:20 PM, Ian Hickson wrote:
> > > Or does "stop the currently running task" in #spin-the-event-loop
> > > imply a jump to step 2 of the algorithm under #processing-model2?
> >
> > Yes.
>
t the spec should say; if this turns out to
be popular and effective, we should reconsider adding it to the language.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ease don't hesitate to raise
them.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
argue that is :enabled, but
I don't think one would argue that is :enabled. Case in point,
nobody argued that should match :enabled before we added the
disabled="" attribute to it.
--
Ian Hickson U+1047E
ny feature, we should ask what the use case is.
On Sat, 11 Sep 2010, Boris Zbarsky wrote:
>
> Something like matchesSelector is an api on the element itself that does
> what you want; do we really need another api for it?
Boris and Jonas make strong arguments here, so I haven't change
he elements must be flow
content", where the terms are from the syntax section of the HTML spec,
except for "flow content", which is from the elements section.
In practice of course exactly what's allowed where depends on what you put
where, which is why the spec doesn't def
the spec to match what the majority of implementations do in due
course, if that changes. Currently it seems to be a bit of a mixed bag.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
aware of, but they get processed
specially in the parser, and aren't considered "real" elements. (They are
documented, though.)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Fri, 3 Sep 2010, Mounir Lamouri wrote:
>
> It looks like the reset algorithm for input elements is considering all
> types except the . Shouldn't "empty the list of
> selected files" be added?
It looks like this has been fixed.
--
Ian Hi
On Tue, 31 Aug 2010, Christoph P�per wrote:
>
> I�m not sure, but I think it�s at your end that character encodings get
> garbled.
Yes, I am unfortunately using an encoding-impaired MUA.
> Ian Hickson:
> > On Tue, 24 Aug 2010, Christoph P�per wrote:
> >>
> >&
On Tue, 31 Aug 2010, Anne van Kesteren wrote:
> On Tue, 31 Aug 2010 01:58:52 +0200, Ian Hickson wrote:
> > On Sat, 7 Aug 2010, Anne van Kesteren wrote:
> > > 2) Is there any reason we cannot also use this "no browsing context"
> > > clause to define documen
y leap-frog each other, roughly in
sync with implementations. This ensures that the whole platform doesn't
ever get too far ahead of implementations, and it ensure that we don't go
too far into the weeds with a bad idea before stopping.
The remainder of this thread discussed the pros and cons of having
localise times. This issue will be decided by the market one way or the
other; it's not clear to me that we can make progress on it here.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
n
> if the required attribute is present on select.
Right, the label doesn't have to be present. Why would we require one?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 24 Aug 2010, Boris Zbarsky wrote:
> On 8/24/10 6:13 PM, Ian Hickson wrote:
> > So basically, translating this to specese:
> >
> > Document objects on which you call open() have an "override reload"
> > flag set and an initially empty source ca
not a meaningful UI decision beyond the visual. That is, a
user should not be worried that opening a different tab is going to change
what happens.
As such, it's always equivalent to just showing all the tab panels one
after each other with a heading.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ent, and one where it's considered metadata
content, with appropriate restrictions on the latter. With such a set of
definitions in place, the HTML spec's model would just work (it already
refers to the content model of as just "metadata content", for
instance).
--
Ian Hi
On Thu, 26 Aug 2010, Christoph Päper wrote:
> Ian Hickson:
> > On Wed, 4 Aug 2010, Thomas Koetter wrote:
> >>
> >> What strikes me though is that according to the spec "The br element
> >> represents a line break". A *line* break is presentational
the specs? (after 5 years of proposed status
> it's kinda time to decide right?)
There's work ongoing to decide exactly how the registry for rel="" values
is going to work; I intend to wait until that is resolved and then letting
the appropriate process/communit
he multiple specs). But I
> think the original question (and, at least, my response to that
> question) was speaking of just the html spec, and revisions of it,
> itself.
Think about how HTML has been developed in the past 7 years. We've had
only one
On Wed, 25 Aug 2010, Anne van Kesteren wrote:
> On Wed, 25 Aug 2010 01:00:50 +0200, Ian Hickson wrote:
> > On Thu, 29 Jul 2010, Anne van Kesteren wrote:
> > > On Wed, 28 Jul 2010 01:32:13 +0200, Ian Hickson wrote:
> > > > I've been working under the assu
peration; for example GC can happen, even multiple times, during a
> property get or set). That would be pretty broken behavior.
The spec says that basically anything you can observe in the DOM is a
strong reference, including e.g. frameElement. So there's no race
condition here.
On Fri, 27 Aug 2010, Olli Pettay wrote:
>
> One thing not too clear in the "magic iframe" approach is that how
> session history works; how is the session history from the iframe merged
> to the new one, especially if the iframe moves to a new document.
This is as well-defined in the spec as it is for the case of sibling
iframes that aren't ungrafted, actually.
> Another thing, which is more implementation depended problem, is that
> how the plugin native widget reparenting works, in case the iframe uses
> plugins.
This is already a problem since you can move an around directly.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
e.g. say that the default actions
> should not occur, but propagation continues)?
The verb "to cancel" seems to be the operative terminology used by the
DOM3 Events specification for this.
--
Ian Hickson U+1047E)\._.,--..
That was for a different section, which no longer exists (and for which
citing the RFC normatively was superfluous, since no normative conformance
criteria from the RFC applied to that section).
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
eneral has been in some flux and the
implementations are all somewhat away from interoperable.
On Thu, 26 Aug 2010, Aryeh Gregor wrote:
> On Thu, Aug 26, 2010 at 2:00 PM, Ian Hickson wrote:
> >> * marquee.direction
> >
> > What do browsers do for this one?
>
> See
On Tue, 17 Aug 2010, Julian Reschke wrote:
> On 17.08.2010 10:36, Ian Hickson wrote:
> > ...
> > The note is lower down. It reads: "Note: The above algorithm does not
> > guarantee that the output will be a conforming Atom feed. In
> > particular, if insufficien
ollow any concrete policy. HTML uses pretty much
every naming convention you can come up with _somewhere_. When adding new
features generally I just try to find an existing feature with a similar
concept and then use the same naming scheme. So e.g. looking at recent
additions, suggests , dir="
ve full-disk encryption, or that they
> have read and agreed to a policy that states that they must use
> full-disk encryption. This way, it's the user or the IT department's
> responsibility to ensure that the disk is encrypted securely, not the
> browser vendor which m
tion show that it is possible, show that it can be done in a
secure fashion, show what a reasonable API for it would be, and show that
there is author demand for the feature.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch
based on completeness. New features are added based on either use cases
(i.e. problems that authors or users are facing), or compatibility (i.e.
things that browsers already do). If there are specific events for which
event handler attributes would be useful, I encourage you to request those
sp
to pages that use in this way]
This has been discussed pretty much to death in the past, including
examining existing pages that do this. This proposal does not add new
information to the discussion, so I haven't changed the spec.
--
Ian Hickson U+1047E)\
On Thu, 12 Aug 2010, Mihai Parparita wrote:
> On Thu, Aug 12, 2010 at 4:56 PM, Ian Hickson wrote:
> > On Tue, 27 Jul 2010, Mihai Parparita wrote:
> > > https://webkit.org/b/42861 has more tests, but briefly, the behavior
> > > in the latest stable versions of these
g is in contrast orders of magnitude more
complicated. One can therefore assume with some confidence that it would
not be a good way to achieve practical accessibility in the real world.
Several alternatives exist, as noted earlier: contenteditable="", for
instance, is more or less au
h describes, and it's not clear
that there's a compat reason for any particular behaviour, so I specced
the simpler and saner behaviour. I don't recall if I studied common values
of value="" and start="" on and . (If I did then presumably they
weren't
1601 - 1700 of 5345 matches
Mail list logo
