On Mon, Jan 28, 2013 at 5:41 PM, Jochen Eisinger joc...@chromium.org wrote:
A side-effect of that decision is that permission is a static attribute,
which we can't currently implement in V8 :-/
Not entirely true. We cannot use FunctionTemplate to do this but we
can add the V8 accessor in
The specs for DOM related exceptions has changed a bit over the last
few years. These changes have been made to simplify things, both for
end users and implementers. Fortunately for the spec writers no two
browsers agreed on the behavior, so end users could not depend on the
details of the old
To clarify.
I intend to make changes to WebKit to align our code with the latest
specs where possible.
On Wed, Dec 5, 2012 at 3:29 PM, Erik Arvidsson a...@chromium.org wrote:
The specs for DOM related exceptions has changed a bit over the last
few years. These changes have been made
On Wed, Mar 14, 2012 at 07:08, Seo Sanghyeon sanx...@gmail.com wrote:
However, there doesn't seem to be any progress on this.
I am interested in moving this forward. Is it okay?
Yes. It would be much appreciated.
--
erik
___
webkit-dev mailing list
How about making this a compile time flag or runtime flag so that
Apple Dashboard and iOS can keep it but let other users of WebKit
disable it?
erik
On Tue, Feb 28, 2012 at 22:23, Benjamin Poulain benja...@webkit.org wrote:
On Tue, Feb 28, 2012 at 9:48 PM, t...@codeaurora.org wrote:
I think the order as specced at
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-focusevent-event-order
is fine. It seems to solve the ordering from a backwards compatibility
case.
The spec leaves out when document.activeElement is changed though.
erik
On Mon, Jul
On Mon, Oct 19, 2009 at 18:03, Oliver Hunt oli...@apple.com wrote:
On Oct 19, 2009, at 5:18 PM, Erik Arvidsson wrote:
I'm trying to clean up some inconsistencies with when keypress events
are dispatched.
WebKit's key event model is modeled to be compatible with Internet
Explorer
I wrote a simple tool that allows me to quickly look up the WebKit
build number based on an SVN revision number.
http://webkit-util.appspot.com/rev/
http://webkit-util.appspot.com/rev/45980
I wrote this mainly so I could figure out what WebKit build number to
check for in our JS library when a
On Sun, Oct 18, 2009 at 16:22, Darin Adler da...@apple.com wrote:
On Oct 18, 2009, at 4:14 PM, Erik Arvidsson wrote:
I wrote a simple tool that allows me to quickly look up the WebKit build
number based on an SVN revision number.
http://webkit-util.appspot.com/rev/
http://webkit
On Sun, Oct 18, 2009 at 16:38, Mark Rowe mr...@apple.com wrote:
It looks like it could be useful, but it has a number of problems that
would make me wary of relying too heavily on it.
For starters, the WebCore version is not exposed to web content at all so
it does not make sense to use
I assume you mean window.navigator?
I think this is a good idea. You should bring this up the WHATWG as well.
2009/7/22 Jungshik Shin (신정식, 申政湜) js...@chromium.org:
Hi,
I proposed exposing the values of the Accept-Langauge list via
window.navigation.acceptLanguages at
11 matches
Mail list logo
