On Tue, 4 Oct 2011, Julien Chaffraix wrote:
>
> following WebKit's attempt at implementing the behavior of |sheet| and
> |disabled| per HTML5 / CSSOM [1], we have found that the specs [2] [3]
> either under-specify the behavior or do not match what browsers are
> doing.
The spec has changed a
ually create the drag image until after dragstart
> processing is finished.
Makes sense.
Seems more useful to support what Rafal is trying to do, though, so I
haven't currently changed the spec for this.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ention of using the data-* attributes so, something like:
>
>
> or
>
>
>
> Would you agree that this is the better option?
If what you want is a tooltip, then the title="" attribute is probably
your best bet. No need for any scripting.
--
Ian Hickson
refox is correct here, and WebKit and Opera are wrong. (I didn't
test IE.)
I recommend filing bugs.
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
a form is valid even when
> it contains invalid data for input types the browser doesn't understand.
> (Like the string 'asdf' in an input type=number field in Firefox.)
You can test using (input.type == input.getAttribute('type')).
--
Ian Hickson
On Sun, 25 Sep 2011, Thomas Broyer wrote:
>
> Is there really no equivalent to the beforeunload event for the History
> API? Has it been discussed? or is this an oversight?
Does the "pagehide" event do what you mean?
--
Ian Hickson U+1047E)\._
On Fri, 23 Sep 2011, Ojan Vafai wrote:
> On Fri, Sep 23, 2011 at 11:49 AM, Ian Hickson wrote:
> >
> > If they're focusable at all, I don't see why they wouldn't be
> > autofocusable. Is there a use case for special-casing read-only ones?
>
> Right.
e
placeholder="" is shorter, shown as part of the input feature, typically
only when there's no input already, and would be specifically about the
input format.
In practice, on visual media, this means title="" is a tooltip and
placeholder="" is an inl
even in a element. Otherwise, things
would stop working if you did:
My Section
My subsection
The rank concept is used to figure out the relative level of the headings
in the document as a whole, it's not the end of the story. You can't just
ignore the outline section,
On Wed, 14 Sep 2011, Martijn wrote:
> On Jan 15, 2008 8:51 AM, Ian Hickson wrote:
> > On Thu, 17 May 2007, Martijn wrote:
> > >
> > > Is how to render shadows defined here?
> > > http://www.whatwg.org/specs/web-apps/current-work/#shadows0
> > > So with
ge collected while they are delaying
> the load event, or to say that they do not delay the load event.
Done for .
and already had requirements to this effect.
outside a document doesn't initiate a load, so it's case is
different.
Let me know if I missed a
nd why this is the case. Can you elaborate?
> 2. For threaded conversations, there would be a lot of nesting.
> Nesting in and of itself is not a bad thing but when trying to syndicate
> the original (parent) , this becomes difficult. Afor="thearticle"
d=57185 following that spec
> doesn't make sense for editable content, there's no Drop event if the
> DragOver isn't canceled and then the default behavior of drag&drop
> doesn't work.
Why would there be no 'drop' event?
--
Ian Hickson
higher resolution than my desktop, but
windows on my desktop typically have far more pixels.
> Ergo, you lose the accessibility because you now can't textually
> represent it in the alt tag.
I don't really understand the use case here. Could you elaborate, ide
me-Options doesn't solve the problem here.
Why would a sensitive site allow itself to be framed by non-same-origin
pages anyway?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
t float first), so it had to be changed.
> (http://html5.org/r/5373 first, then changed again because of
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10799 to be consistent
> with filtering behaviour.)
On Mon, 8 Aug 2011, Jeff Muizelaar wrote:
> On 2011-08-08, at 4:58 PM, Ian Hic
ot clear to me which spec this feedback is intended for. Could you
elaborate on which specification you would like to change for this? (It
may be that this is the wrong mailing list.)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
n that wanted to share common code here would be
able to already.
On Fri, 5 Aug 2011, Jonas Sicking wrote:
>
> Sounds good. I'm for such a change yes.
There are two possible changes here: making the HTML spec's definition of
parsing numbers use Unicode's varying definition
On Sat, 30 Jul 2011, Jukka K. Korpela wrote:
> 30.07.2011 01:39, Ian Hickson wrote:
> > On Sat, 30 Jul 2011, Jukka K. Korpela wrote:
> > > 29.07.2011 23:56, Ian Hickson wrote:
> > > > >
> > > > > Anyway, aren't you saying that says "th
On Sat, 30 Jul 2011, Cameron McCormack wrote:
>
> Jumping in the middle of this thread to pick up on one aspect...
>
> On 28/07/11 6:15 PM, Ian Hickson wrote:
> > Are we really concerned about objects stringifying to "[Object Foo]"?
> >
> > It seems that t
On Fri, 29 Jul 2011, Jonas Sicking wrote:
> On Fri, Jul 29, 2011 at 8:32 PM, Ian Hickson wrote:
> > On Fri, 29 Jul 2011, Jonas Sicking wrote:
> >>
> >> I have no idea how the UA would be smart enough to figure out if
> >> filtering makes sense or not based on
nsitive.
> All other attribute values are case-sensitive.
The spec changed recently in response to Anne's efforts here. If this is
an area of interest, I encourage you to study the specification to see if
the current requirements are satisfactory.
--
Ian Hickson
On Tue, 26 Jul 2011, Jukka K. Korpela wrote:
> 25.07.2011 22:02, Ian Hickson wrote:
> > >
> > > So what markup should we use for E = mc�, given that by the
> > > applicable standards, E, M, and c should appear in italics and the
> > > other characters
t; If you want OS-level notifications you might be interested in [1]
>
> [1] http://dev.w3.org/2006/webapi/WebNotifications/
Indeed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
roaching browser vendors about this. I don't think we need
changes to the spec to handle this today.
I'm not sure pages would adopt a solution, either. It might be worth
approaching high-profile sites that do this and asking them whether
they're interested in doing it in a different way.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ans
> "anything we want to add outside the html spec" then why not just allow
> any tag, without a prefix, which accomplishes the same thing?).
Because then it would limit the space within which the language itself can
be extended in the future.
--
Ian
I left the option of having the hint even when there's a value since
the value could come from the server (a default) rather than the user.
In general this is a UA UI issue so I don't want to overconstrain this. If
there's a use case for UIs that aren't allowed in the spec as it s
e words, data- attributes are intended to be
> delivered by a server for use by the javascript code that server
> delivers with the page.
Right.
> The exhibit attributes are not associated with any server, and are not
> associated with any particular data items being delivered by any server.
> Rather, they are part of "generic software not associated with" the
> server (see quote above) and handle _presentation_ of the content on
> the page.
>
> So, while it might be technically valid to use data- prefixes, it
> doesn't seem to fit the intention.
Is the exhibit JavaScript library not being delivered with the page?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Sat, 16 Jul 2011, Jukka K. Korpela wrote:
> 16.07.2011 00:01, Ian Hickson wrote:
>
> > Much discussion on this topic happened when we started on this work in
> > 2004 and 2005, I highly recommend perusing the archives around that
> > time.
>
> Authors and imp
t it states that plugins can only be loaded if it's done in a
> manner that ensures that all other requirements are still fulfilled.
I have since done this.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 12 Jul 2011, Boris Zbarsky wrote:
> On 6/13/11 8:09 PM, Ian Hickson wrote:
> > > It's possible to switch these relevant checks to walk the
> > > ownerDocument chain instead, say. Then we need to audit all the
> > > callsites to make sure this make
gt;
> Really, since there are no browser implementations yet, it's best to
> *not* use it yet. Without any feedback in the form of actually seeing
> it work, there's a good chance you'll accidentally get it wrong. As
> well, your early use of it counts as legacy usage if we decide that,
> upon attempting to implement it, it needs to be changed.
Indeed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Thu, 15 Dec 2011, Boris Zbarsky wrote [edited for context]:
> On 12/15/11 3:10 PM, Ian Hickson wrote [edited for context]:
> >
> > I might be open to changing the current spec text -- presumably to
> > just define as follows, or something similar (though using
>
only,
> and have them both return the same URL concept, which defaults to
> "about:blank".
They now always return about:blank, since this URL concept is never set.
So um... when should it be set? Is it just "the document's address" but
- to - HTML converters out there. I recommend doing
a search for "word to html" in your favourite search engine.
HTH,
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things th
n only someone who's really interested will make
> the efforts of signing up to the mailing list and asking how it's done.
I made a change a few weeks ago to try to improve matters without going
too far, so now if you hover over the boxes you get an "edit" link.
Hopefully
t's reflected regardless of the type:
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html#dom-input-placeholder
>
> "does not apply to the element" could use clarification, though.
On Thu, 23 Jun 2011, Ian Hickson wrote:
>
> It&#
On Mon, 20 Jun 2011, Jonas Sicking wrote:
>
> "complete" seems like the most useful and consistent value which would
> seem like a good reason to require that.
Jonas is correct. Since there was no interop here I figured we might as
well go with what made sense.
On Wed, 11 Jan 2012, Ian Hickson wrote:
> On Wed, 15 Jun 2011, Lachlan Hunt wrote:
> > On 2011-06-15 07:55, Ian Hickson wrote:
> > > On Mon, 28 Mar 2011, Lachlan Hunt wrote:
> > > > This should also only allow up to 3 digits representing
> > > > m
On Wed, 15 Jun 2011, Lachlan Hunt wrote:
> On 2011-06-15 07:55, Ian Hickson wrote:
> > On Mon, 28 Mar 2011, Lachlan Hunt wrote:
> > > This should also only allow up to 3 digits representing
> > > milliseconds. If there are 4 or more digits (microseconds or
> >
k to your earlier feedback on this so that
I can audit why it never received a response?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 14 Jun 2011, Markus Ernst wrote:
> Am 14.06.2011 09:32 schrieb Ian Hickson:
> > On Fri, 11 Mar 2011, Markus Ernst wrote:
> > >
> > > Instead of a new paragraph concept, there could also be a new
> > > concept for inline (resp. Phrasing Content) lists
first argument,
> and the new value as the third argument.
> ---
>
> The current value of the selectionEnd attribute is not as the first
> argument, but as the second argument, is it?
Indeed. This has been fixed. Thanks.
--
Ian Hickson U+1047E
Microsoft invented back
in the late 90s in COM, which is what this is originally based on, if I'm
not mistaken.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
is
> optimization and how much time would be saved. It's surprisingly large.
Any news on this? If Chrome was able to do this, it would be worth putting
in the spec to give cover to other browsers interested in the same
potential performance improvement.
--
Ian Hickson U+
On Fri, 10 Jun 2011, Mounir Lamouri wrote:
> On 06/04/2011 12:57 AM, Ian Hickson wrote:
> > On Thu, 17 Feb 2011, Mounir Lamouri wrote:
> > > According to a comment of Hixie in [1], this case has been handled by
> > > the specs in 2004 but it doesn't seem to be any
lementation experience we
need to make progress on this issue.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
t; all. So either rel="next" must be relaxed here, too, or we need a new
> attribute. I'm fine with either choice.
The relationship between a page and a page obtained through form
submission is always "it's the page that was generated from the form
submission"; I'm not sure it makes sense to have rel="" on buttons.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
#x27; and 'load'. I haven't changed
'pageshow', so you could still get code running between 'load' and
'pageshow'. Let me know if you think we should merge those into one task
as well.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 5 Jul 2011, Robert O'Callahan wrote:
> On Tue, May 31, 2011 at 9:40 AM, Robert O'Callahan
> wrote:
> > On Fri, May 13, 2011 at 5:53 PM, Ian Hickson wrote:
> >
> >> On Fri, 13 May 2011, Robert O'Callahan wrote:
> >> >
> >> &
> probably be easiest for me, but perhaps there is a better way.
I believe this has since been fixed; the spec now uses MessagePort[] as
the type for MessageEvent.ports.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Sat, 7 Jan 2012, Smylers wrote:
> >
> > If it's something you'd find useful even in its incomplete state, I
> > can add an alternative style sheet
>
> Yes, please.
Roger. I've added an alternative style sheet set that has a rule for .impl
feature.
If it's something you'd find useful even in its incomplete state, I can
add an alternative style sheet or make the ?style=highlight URL show the
annotations that are present, though. It wouldn't be something we'd
advertise but if it's
On Mon, 16 May 2011, Adam Shannon wrote:
> On Mon, May 16, 2011 at 18:39, Ian Hickson wrote:
> > On Mon, 16 May 2011, Adam Shannon wrote:
> >>
> >> I don't like having the only barrier between changing the default
> >> search engine for a user&#x
/popupbase.js&q=activeElement%20package:http://closure-library%5C.googlecode%5C.com&l=477
>
I've clarified the spec to say that when the browsing context in an iframe
has focus, the iframe itself by definition is the element with focus in
the parent browsing context.
--
use case, in your data chart, could quite easily have been written
> up without the added attribute. That's why I'm bringing this up.
It could have been done, but I probably wouldn't have bothered if it
wasn't an extra argument.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Tue, 19 Jul 2011, Boris Zbarsky wrote:
> On 7/19/11 9:12 PM, Ian Hickson wrote:
> > Would other browser vendors be willing to change to only look at > href> in?
>
> Gecko used to implement that back when the spec said it.
>
> This caused site compat issues. See
&
dition to just a
> Blob, for more general utility.
>
> I suggest you bring it up on public-webapps@, where that spec lives.
> http://dev.w3.org/2009/dap/file-system/file-writer.html#idl-def-FileSaver
I agree that an API like FileSaver is the right way to do this. Using
wouldn't
On Wed, 14 Dec 2011, Boris Zbarsky wrote:
> On 12/14/11 7:12 PM, Ian Hickson wrote:
> > One could actually argue that the pages that exist that use _main and
> > _content actually work _better_ in current UAs with those values being
> > interpreted as browsing context nam
On Wed, 14 Dec 2011, Boris Zbarsky wrote:
> On 12/14/11 8:05 PM, Ian Hickson wrote:
> > it was with respect to, which we now
> > define in terms of 'white-space'.
>
> Maybe that needs to change?
How else would we define it?
Whether it's or that gets def
area without
knowing how safe it is. This kind of thing can radically affect how pages
render, especially old pages that aren't being maintained any more.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Fri, 13 May 2011, Boris Zbarsky wrote:
> On 5/13/11 4:46 PM, Ian Hickson wrote:
> > The sum total of what the spec has to say on the matter is "User
> > agents may support secondary browsing contexts, which are browsing
> > contexts that form part of the user agent&#
On Fri, 13 May 2011, Simon Pieters wrote:
>
> We're making this change in Opera (we'll ignore "space characters" in
> atob).
I've updated the spec accordingly. Let me know if this causes any
problems.
--
Ian Hickson U+1047E
ery useful to allow wildcards in the data type, so instead
> of defining multiple types for images, "image/*" should be allowed.
Well you'll have to pick a specific type when you actually receive the
drop, so it seems simpler to just list the supported types. Otherwise you
might
> Similarly, what should the tokenizer do if the document.write emits half
> of a UTF-16 surrogate pair as the last character?
Can you elaborate on what difficulty this would present?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/
ot; or "in caption" will have the same effect
here.
> Perhaps the spec could be modified to add a definition for "act as if"
> along with the definition for "using the rules for".
I've added a paragraph that mentions a definition for "act as
ing element referenced above is removed before the bookmark is
used. Thus the bookmark is literally keeping track of the position of the
formatting element itself, as if it was itself the bookmark. You can
picture this as the bookmark being wrapped around the formatting element.
HTH,
--
Ian
t; was used as a technical term, and
> > was not called an empty element.
>
> It seems reasonable to call it empty. It matches XML's definition of
> "empty". http://www.w3.org/TR/xml/#dt-empty
Indeed.
On Mon, 29 Aug 2011, Bronislav Klu�~Mka wrote:
&g
flag.
>
> And in the in table insertion mode, when a character token is inserted,
> and the text_integration_mode flag is set, then just process the token
> using in body mode, and otherwise follow the directions that are there
> now.
>
> I'm not sure
s a definition that gives
an authoring conformance criteria. The second sentence doesn't say
anything normative at all; it just describes the meaning of the attribute.
The spec tries to be very explicit about stuff. You should never have to
read between the lines.
--
Ian Hickson
minus one" (omitting spec text that
doesn't apply here regarding the value="" attribute and the reversed=""
attribute -- see the spec for precise rules).
> The spec seems to say that it should stop a 1 but then what value I
> sho
Nowadays we solve this with a .current or .active class name.
>
> Not exactly life-changing, but useful nonetheless.
This may be of interest:
http://dev.w3.org/csswg/selectors4/#local-pseudo
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
t will need to be designed to
> integrate with other streaming APIs in the platform, e.g. the audio and
> video stuff that is currently being discussed (mostly elsewhere).
Indeed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
s Jr. wrote:
>
> Just put an @itemref on each , pointing to the s that are part
> of that column. It's more verbose, but it doesn't rely on special
> HTML-only rules.
That's a possible workaround for now, true.
--
Ian Hickson U+1047E)\.
y the that I removed in the quote above:
> http://schema.org/Person";>
> This book has been authored by
>
> http://smith.org/john";>John
> Smith
>
>
The microformats for this particular case is shorter still.
I haven't
es the Microdata model
> kind of odd if a property is both an item and has a fallback text
> representation. It will also mask the fact that a text property has been
> upgraded to an item, somewhat decreasing the chance that the consuming
> code will be updated.
Yeah. And authors would have to make sure the textContent is usable as
fallback, which isn't at all a given, IMHO.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Sat, 9 Jul 2011, Philip Jägenstedt wrote:
> On Sat, 09 Jul 2011 01:19:02 +0200, Ian Hickson wrote:
> > On Sat, 9 Jul 2011, Philip Jägenstedt wrote:
> > >
> > > Step 11 is "If current has an itemprop attribute specified, add it
> > > to results.&q
methods we have now.
Ideally, it would be good to have the current protocol and content type
handlers and the Web Intent stuff all use a coherent and consistent API.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _
nt for machine-readable data, , as well as an
element specifically for time-related machine-readable data, .
The old element, with its rendering rules and DOM API, are gone.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A
vent-stream;
>
> Are we sure we want this strict checking of media type parameters? I
> always thought the media type itself was what strict checking should be
> done upon, but that its parameters were extension points, not points of
> failure.
Fair enough. I've changed the spe
ill not pass Origin through (I do
> not really know if there are any). Thanks
FWIW, I've since changed the spec so that you can specify whether to send
credentials or not. When credentials aren't sent, you can use the * form.
--
Ian Hickson U+1047E)\._
follow
the aforementioned group.
On Tue, 26 Jul 2011, Mark Callow wrote:
> On 26/07/2011 14:30, Ian Hickson wrote:
> > On Thu, 14 Jul 2011 04:09:40 +0530, Ian Hickson wrote:
> > > > > >
> > > > > > Another question is flash. As far as I have seen
On Wed, 23 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 7:40 PM, Ian Hickson wrote:
> > If people could e-mail me the lists of topics they would be interested in
> > being e-mailed diffs for, it would give me a good idea of what coarseness
> > would be helpful here, and t
riptions" button at the top
right of the spec, and follow the on-screen instructions.
I haven't fully tested this yet so if you run into any problems, e.g. I
spam you every last edit fifteen times over, let me know.
--
Ian Hickson U+1047E)\._.,--,'``
e could e-mail me the lists of topics they would be interested in
being e-mailed diffs for, it would give me a good idea of what coarseness
would be helpful here, and thus whether this is a realistic idea.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://
person who requested the change in the first place.
Indeed. I often don't even know whether the people asking are browser
vendors or not, in fact, let alone with which they are affiliated. :-)
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixi
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 3:39 PM, Ian Hickson wrote:
> > If you can tell me which pieces those are, I can see what I can do
> > about updating the annotations mechanism to make those checkins easier
> > to filter out.
>
> That's
On Mon, 21 Nov 2011, Boris Zbarsky wrote:
> On 11/21/11 3:26 PM, Ian Hickson wrote:
> > > What's needed is a way to notice when changes to a particular piece
> > > happen. There isn't one.
> >
> > Which pieces do you _not_ want to be notified of chang
ather pressing one), I would be more than happy to support such an effort
in whatever way I can.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
ted
all the way down, and despite there only being one style declaration.
I think we could argue either as being better than the other. There's no
security problem here (the scoped style can only hurt its own content) and
in practice fonts are typically given pretty unique names, so clash
for non-CORS cases doesn't really apply any more. I
should strip those other entries.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
origin along with it, but any
> mutation (and all new strings) switch to "other specs"?
In all three cases here, the image was generated from a URL found in the
src="" content attribute of the element created by the script. The
image data is C
el pressured to show the UA menu
because of this?
In general, there's also the need to not add features so fast that the
feature set in different browsers is completely different due to them each
implementing their own subset of the spec. This is one reason to keep the
spec gr
ce all remaining U+000D CARRIAGE RETURN characters by
> > + U+000A LINE FEED (CRLF) characters.
>
> Same: should this just be (LF)?
Thanks. Fixed.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
On Thu, 20 Oct 2011, Ryosuke Niwa wrote:
>
> How about UndoableTransaction? Or DOMTransaction?
Either works for me. Just pick one and go with it. :-) So long as it's not
something that could be very confusingly used by other APIs (or indeed by
user code) it doesn't matter
ished that we are going to another document (i.e. not
just for #fragment navigations). Should it happen before or after
onbeforeunload and onunload? Should it just happen when the session
history is updated (i.e. when the page load changes the rendering), or at
some oth
> things are important, we should have references to them at least. Or
> include them in this spec, with a note to move them into their new homes
> once we agree on the spec.
I haven't yet added them to the spec. I'm sure Anne will add links once I
have. :-)
Ann
; too. (Other tests don't fail here because they don't happen to have two
> of the same tags on the stack). This means that the element ends
> up as a child of the element instead of the outer element.
That should be fixed with the updated spec text now, right?
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
fied to add a definition for "act as if"
> along with the definition for "using the rules for".
I'll fix it. Quickly though, the answer is that it uses the current actual
mode, but in practice I wouldn't be surprised if it actually made no
difference (I haven&#
On Thu, 6 Oct 2011, Bjartur Thorlacius wrote:
> On Wed, 05 Oct 2011 17:37:22 -0000, Ian Hickson wrote:
> > On Wed, 5 Oct 2011, Simon Pieters wrote:
> > >
> > > video and audio should have controls="" and autoplay=""
> >
> > The spec
1201 - 1300 of 5345 matches
Mail list logo
