What's the right thing to do for something that is in a CR spec, but the
draft spec for the next version has it behave differently? Specifically, in
Selectors 3, :not only accepts a single simple selector. In Selectors 4, it
accepts a comma separated list of compound selectors (a superset of the
Hi,
I'd appreciate it if the webkit-changes maintainer(s) could consider the
following.
Can the subject line of a webkit-changes message be changed, for example,
from:
[webkit-changes] [82407] trunk/Tools
to:
[webkit-changes] [82407] make webkit-patch upload respect -d
?
That is,
Hey,
I try to build WebkitGTK and on various revisions I get errors similar to
that one: https://gist.github.com/894025
I have version 2.28 of glib and installed all of the dependencies from
sources, cause I use homebrew for installing packages (usually latest ones).
Should I try some older
This is not the right mailing list for discussion of how to use WebKit or work
around bugs. This mailing list is for people involved in the development of
WebKit to work together. For an GTK-specific issue I suggest webkit-gtk
mailinglist. See http://www.webkit.org/contact.html.
- Patrick
Am
If you have not heard about 'reftests', please see the following wiki entry
about reftests in WebKit:
https://trac.webkit.org/wiki/Writing%20Reftests
The new-run-webkit-tests now can run reftests in default.
You can see the sample reftest here:
http://trac.webkit.org/changeset/81644
I'm
If the change is backwards compatible (i.e. if you don't break the behavior
described in Selectors 3), then I don't think it needs to be prefixed.
What have other vendors done?
Simon
On Mar 30, 2011, at 12:05 AM, Ojan Vafai wrote:
What's the right thing to do for something that is in a CR
On Fri, Mar 25, 2011 at 1:08 PM, Peter Kasting pkast...@google.com wrote:
On Fri, Mar 25, 2011 at 1:03 PM, Mark Rowe mr...@apple.com wrote:
Safari 5.0.3 will always report a build version of 533.19.4. Safari 5.0.4
will always report a build version of 533.20.27. You already used the former
Yeah, I'd prefer not to prefix :not. (Haha.)
In fact :not used to actually support more complex selectors, and I had to dumb
it down to pass stupid CSS 2.1 tests that deliberately checked for the lack of
complexity... so all we'd be doing is going back to our old behavior. We
should
I am wondering what the webkit community thoughts are with respect to
possibly evolving the sunspider benchmark.
I have worked with webkit based browsers and various javascript engines
shipping on mobile devices today and am seeing some very peculiar behavior
now starting to show up. As the
9 matches
Mail list logo
