On Jun 16, 2011, at 4:14 PM, Tab Atkins Jr. wrote:
> On Thu, Jun 16, 2011 at 1:48 PM, David Hyatt wrote:
>> Do you actually mean try out both ":scope" tacked on to the end of the rule
>> as well as ":scope " (note the space indicating a descendant selec
Do you actually mean try out both ":scope" tacked on to the end of the rule as
well as ":scope " (note the space indicating a descendant selector) tacked on
to the beginning?
So for example, #foo { } would turn into #foo:scope, :scope #foo { } thus
allowing it to match either the scope or a des
It is considered a bug.
On Dec 9, 2009, at 4:57 PM, Jonas Sicking wrote:
> On Wed, Dec 9, 2009 at 2:10 PM, James Robinson wrote:
>> 2009/12/9 tali garsiel
>>>
>>> Well, not completely.
>>> Regarding the first question- Webkit guys told me (on their IRC channel)
>>> that the don't block the par
On Dec 9, 2009, at 4:10 PM, James Robinson wrote:
> 2009/12/9 tali garsiel
> Well, not completely.
> Regarding the first question- Webkit guys told me (on their IRC channel) that
> the don't block the parser and only block scripts that request visual
> information, so I'm still confused.
>
>
This is false. WebKit will block the parser when it encounters an external
script if there are pending stylesheet loads. However we have a speculative
preloader that will continue to parse and load resources beyond that script
(but the real parser will be blocked).
dave
On Dec 9, 2009, at 3:
I agree.
dave
On Jun 19, 2008, at 8:05 AM, Philip Jägenstedt wrote:
Safari already uses a transparent background by default and to me that
doesn't seem like a bad idea -- it may be best to hide small 1px
letterboxes due to rounding errors in aspect ratio calculation etc.
Setting "background-co
On Jun 2, 2008, at 4:57 PM, Vladimir Vukicevic wrote:
On Jun 2, 2008, at 2:39 PM, Oliver Hunt wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the platform to determine what
On Jun 2, 2008, at 4:34 PM, Vladimir Vukicevic wrote:
Yeah, I agree -- I thought that there was some plan somewhere to
uplift a bunch of these SVG CSS properties into general usage? I
know that Gecko uplifted text-rendering, we should figure out what
else makes sense to pull up. (If image
I like the idea of this property. I actually would love to see the
SVG property applied to HTML as well. :)
dave
On Jun 2, 2008, at 4:15 PM, Vladimir Vukicevic wrote:
Sure; bilinear filtering is slower than nearest neighbour sampling,
and in many cases the app author would like to be ab
Also as Maciej said earlier, we at Apple did not ask that the SHOULD
wording be removed and had stated we could live with it.
dave
On Dec 12, 2007, at 1:12 PM, David Hyatt wrote:
On Dec 12, 2007, at 6:38 AM, Elliotte Rusty Harold wrote:
David Hyatt wrote:
Fear of submarine patents is
On Dec 12, 2007, at 6:38 AM, Elliotte Rusty Harold wrote:
David Hyatt wrote:
Fear of submarine patents is only one reason Apple is not
interested in Theora. There are several other reasons. H.264 is a
technically superior solution to Theora. Ignoring IP issues, there
would be no
SHOULD is toothless. It carries absolutely no weight. I don't think
it's appropriate for such weak language to be in the HTML5 spec. It
should either be a MUST (which is inappropriate at this juncture for
reasons that Dave Singer. Ian Hickson and myself have posted about in
previous mess
On Dec 11, 2007, at 3:46 PM, Manuel Amador (Rudd-O) wrote:
Apple and Nokia seem to think that there *are* hamburgers in the
moon, and
that those hamburgers will cost them billions of dollars in submarine
sandwich lawsuits.
Of course, that's what they are *saying*. It doesn't take a Feynman
I can give you my opinions. Not sure if they match up with Ian's or
not. :)
On Jun 6, 2007, at 2:41 AM, Henri Sivonen wrote:
* When the data source was initialized from the DOM, will changes
to the datagrid be reflected back to the DOM?
I would expect a DOM data source to be updated.
We'd have to decide if reopens across closures of .
dave
On May 29, 2007, at 3:57 PM, Anne van Kesteren wrote:
On Wed, 30 May 2007 00:11:22 +0200, David Hyatt <[EMAIL PROTECTED]>
wrote:
WinIE allows it, and we just changed WebKit to allow it too.
So what exactly do you do whe
WinIE allows it, and we just changed WebKit to allow it too.
dave
If were to be standardized, Apple would need this
done in a way that would be backwards-compatible with our current
syntax. Otherwise we'd be forced to require an opt-in mode for HTML5
(and that is really not something we want to have to do).
dave
([EMAIL PROTECTED])
On May 17, 2007, at
+1. Agree with Hixie.
(ducks)
On Apr 30, 2007, at 1:19 PM, Ian Hickson wrote:
On Sat, 28 Apr 2007, mozer wrote:
+1
On Sat, 28 Apr 2007, David Hyatt wrote:
+1 also.
Please don't send e-mails with just "+1" (or "-1") to this mailing
list.
While I know it se
+1 also.
On Apr 28, 2007, at 3:49 AM, mozer wrote:
+1
On 4/28/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote:
How about about adding a toggle() operation to classList? Adds the
token if
not present, removes it if present. This would be useful for
script code
that dynamically manipula
I am not sure that should be left up to some unspecified heuristic
though. There's also the issue of wanting to display a dropped file
at the correct position within the DOM.
I like the idea of having a way of associating a file upload control
with a contenteditable region and I also like
I agree with this. The tag isn't worth much to the Web if it's not
interoperable among *all* Web browsers. That includes,
unfortunately, Internet Explorer. That is why I think trying to pick
a baseline format in the WhatWG is premature. Until the
element moves to the HTML WG and we fin
Posting this forwarded message regarding .
dave
([EMAIL PROTECTED])
==
Dear WHATWG and Mr. Hickson,
Apple Computer, Inc. (“Apple”) believes it has intellectual property
rights
(“IP Rights”) relative to WHATWG’s Web Applications 1.0
I'll have much more to say about this in the coming months.
dave
([EMAIL PROTECTED])
On Jan 30, 2007, at 11:44 PM, Rowan Nairn wrote:
Hi, I'm new to the list so I'm not sure if this is beyond scope or not
but has anybody thought about what kind of mouse events we would like
to get, say the iPh
Shipping Safari has no SVG support. WebKit nightlies do. That's the
only reason the logo now renders correctly in the nightlies so
that particular file is completely irrelevant to this discussion.
dave
On Dec 2, 2006, at 2:41 PM, Robert Sayre wrote:
On 12/2/06, Anne van Kesteren <[E
Yeah I see what you mean. In addition to a drawText you probably
want something like a metricsForText API that would tell you the
extent of the string and the font metrics (line height, ascent,
descent, baseline).
dave
On Oct 25, 2006, at 3:10 AM, James Graham wrote:
David Hyatt wrote
ent();
context.getFontDescent();
context.getFontLeading();
context.getTextWidth(string);
Best regards,
Stefan
David Hyatt wrote:
I think a drawText method would be extremely useful.
Rather than specifying stylistic information explicitly (via a
font object), I'd use a special parenthetic
I think a drawText method would be extremely useful.
Rather than specifying stylistic information explicitly (via a font
object), I'd use a special parenthetical pseudo-element. thus
allowing the author to specify the style as for any other element on
a page something like this...
can
Except with something like canvas, people are going to care about the precise pixel-level details of the rendering. We can't handwave these details away using vague terminology like low-quality or high-quality, where the user agent is free to decide what those terms mean. If we do that, then we r
I don't think a totally different context is a good idea. Sometimes you want to mix antialiased and non-antialiased modes.The API in CG is part of the graphics state...CGContextSetShouldAntialiasI don't think an API like this should be vague about what it's doing... e.g., just using vague terms li
The XBL code in the Safari tree is dead. It's not compiled, and it
was based on XBL1 (Mozilla's XBL) anyway.
dave
On Aug 12, 2006, at 7:56 PM, Matthew Raymond wrote:
James Graham wrote:
Matthew Raymond wrote:
What Firefox is doing for DHTML accessibility has a very
narrow use
case. I
I don't think it's intuitive to support chaining only on those
methods that happen to return null right now.
dave
([EMAIL PROTECTED])
On Jul 2, 2006, at 4:01 PM, Ian Hickson wrote:
On Mon, 3 Jul 2006, Håkon Wium Lie wrote:
Anyway, this is all a straw man -- this isn't the reason that the
Strongly agree. :)
dave
On Jun 23, 2006, at 10:09 PM, Lachlan Hunt wrote:
Alexey Feldgendler wrote:
On Fri, 23 Jun 2006 10:22:34 +0700, Lachlan Hunt
<[EMAIL PROTECTED]> wrote:
Roughly what percentage of all use cases would you expect
heuristics and user preferences to give suboptimal resul
The only time spell checking matters is when the user is the one
creating the content (not the author). It doesn't make any sense to
spell check non-editable content that the user didn't even create.
If the content is editable, then spell checking should just be left
up to the preference
If the user wants spell checking on in all textareas, then it should
be on, regardless of what the page says. I don't think the page
should be allowed to override spell checking rules, since this is
really a user decision. For example, I know how to spell, so I don't
want spell checking o
This mail showed up pointlessly out of order. I see Ian already
responded. :)
dave
On Apr 22, 2006, at 6:15 PM, David Hyatt wrote:
The getPixels proposal seems broken to me in that it does not take
into account high DPI, i.e., a situation where the canvas pixel
space has been scaled and
The getPixels proposal seems broken to me in that it does not take
into account high DPI, i.e., a situation where the canvas pixel space
has been scaled and a more detailed image is possibly rendering
within a region of the canvas. In this situation, a "canvas pixel"
could actually be a bu
BTW, not sure if you have this in the WhatWG parsing spec, but a
stray (that does not match some opening ) has to be treated
like an open .
Also, is actually supported even in HTML by
Firefox and Safari. We're stuck with it forever as well, since most
of the Dashboard widgets use in H
BTW, we tried to add as an inline that should be reopened
(like and etc.) and it broke some of our layout tests
(snippets of real-world Web sites). clearly does not always
reopen in WinIE and Firefox, so for now we are having to leave it out.
dave
On Feb 2, 2006, at 11:01 AM, Blanchar
Anything the WHATWG specifies in this area must be largely compatible
with WinIE. If you specify error recovery that would yield
dramatically different results, then nobody is going to implement
it. Safari's algorithm is designed to keep a relatively sane DOM, to
keep the performance snap
We used to not reopen the tags. It was the #1 rendering bug in our
engine. We had over 60 unique duplicates of the bug in our internal
database. All that would happen if we didn't reopen the tags is that
people would switch to another browser. :)
dave
On Jan 25, 2006, at 11:31 PM, Blanc
My 2 cents.
It took me a long time to develop an algorithm that actually fixed
all 60 of the duplicate internal Apple bugs on this subject. I'm
reluctant to revisit this problem in our code base, given that my
current algorithm was developed both to solve the problem and to be
extremely
As a child of a or .
dave
On Dec 7, 2005, at 8:47 PM, Matthew Raymond wrote:
David Hyatt wrote:
Shipping Safari actually supports as separators in
dropdowns now. We needed this for Dashboard widgets that wanted to
be able to put separators into their select UI.
Is that inside an or
Shipping Safari actually supports as separators in
dropdowns now. We needed this for Dashboard widgets that wanted to
be able to put separators into their select UI.
dave
On Dec 7, 2005, at 4:00 PM, Ian Hickson wrote:
Then again, toolbars often have separators, so maybe they're a
ty
The class attribute! So efficient it must be wrong! :)
dave
([EMAIL PROTECTED])
On Nov 8, 2005, at 12:30 AM, Anne van Kesteren wrote:
Quoting Mike Dierken <[EMAIL PROTECTED]>:
[1] http://www.whatwg.org/specs/web-apps/current-work/#profile
Can the 'class' attribute have multiple values? If not
44 matches
Mail list logo
