Re: [webkit-dev] Implementing MathML stylistic attributes in WebKit

On Fri, Sep 25, 2020 at 12:47 AM Frédéric Wang wrote: > On 02/09/2019 16:11, Frédéric Wang wrote: > > Hello, > > Currently MathML attributes mathvariant, displaystyle and scriptlevel [1] > [2] are implemented in WebKit using custom "style resolution" and > "one-glyph rendering" inside the MathML

Re: [webkit-dev] Implementing MathML stylistic attributes in WebKit

On 02/09/2019 16:11, Frédéric Wang wrote: > Hello, > > Currently MathML attributes mathvariant, displaystyle and scriptlevel > [1] [2] are implemented in WebKit using custom "style resolution" and > "one-glyph rendering" inside the MathML layout code [3] [4] [5]. These > features involve text rende

Re: [webkit-dev] Implementing OffscreenCanvas

On 2019-10-17 16:23, Chris Lord wrote: > So I was just looking at adding a setting, but looks like it's already > behind a runtime-setting that's controlled by the experimental-features > flag, so I guess we're ok as it is? After discussing with Zan, we decided the best thing to do was to split

Re: [webkit-dev] Implementing OffscreenCanvas

On 2019-10-11 12:13, Ryosuke Niwa wrote: > On Fri, Oct 11, 2019 at 2:09 AM Chris Lord wrote: > >> On 2019-10-10 23:15, Ryosuke Niwa wrote: >>> On Thu, Oct 10, 2019 at 2:07 PM Myles C. Maxfield >>> wrote: >>> > On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa > wrote: > > Hi Chris, >

Re: [webkit-dev] Implementing OffscreenCanvas

On 11/10/2019 11:09, Chris Lord wrote: > This sounds good to me, I'll file a bug and write a patch for this. I > assume there are ways of enabling features when tests are run? While a > user (or a developer) using WebKit wouldn't want this feature to be > enabled, I think it should be enabled for (

Re: [webkit-dev] Implementing OffscreenCanvas

On Fri, Oct 11, 2019 at 2:09 AM Chris Lord wrote: > > On 2019-10-10 23:15, Ryosuke Niwa wrote: > > On Thu, Oct 10, 2019 at 2:07 PM Myles C. Maxfield > > wrote: > > > >>> On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa > >>> wrote: > >>> > >>> Hi Chris, > >>> > >>> I'm excited that you're working on

Re: [webkit-dev] Implementing OffscreenCanvas

On 2019-10-10 23:15, Ryosuke Niwa wrote: > On Thu, Oct 10, 2019 at 2:07 PM Myles C. Maxfield > wrote: > >>> On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa >>> wrote: >>> >>> Hi Chris, >>> >>> I'm excited that you're working on OffscreenCanvas because I think >>> it would be a valuable feature >> >

Re: [webkit-dev] Implementing OffscreenCanvas

On Thu, Oct 10, 2019 at 2:07 PM Myles C. Maxfield wrote: > > > On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa wrote: > > Hi Chris, > > I'm excited that you're working on OffscreenCanvas because I think it > would be a valuable feature > > > Me too!!! > > , and I'm confident we can come up with a str

Re: [webkit-dev] Implementing OffscreenCanvas

> On Oct 10, 2019, at 12:57 PM, Ryosuke Niwa wrote: > > Hi Chris, > > I'm excited that you're working on OffscreenCanvas because I think it would > be a valuable feature Me too!!! > , and I'm confident we can come up with a strategy to limit its privacy & > security risk as we see fit. >

Re: [webkit-dev] Implementing OffscreenCanvas

Hi Chris, I'm excited that you're working on OffscreenCanvas because I think it would be a valuable feature, and I'm confident we can come up with a strategy to limit its privacy & security risk as we see fit. However, many of your patches seem to ignore the fact most of WebCore objects aren't th

Re: [webkit-dev] Implementing OffscreenCanvas

> On Oct 10, 2019, at 10:18 AM, John Wilander wrote: > >> On Oct 10, 2019, at 9:42 AM, Maciej Stachowiak wrote: >> >> For clarity, it’s already possible to render to a regular canvas offscreen. >> The can be hidden using any of the techniques that can make any >> other canvas invisible. Na

Re: [webkit-dev] Implementing OffscreenCanvas

> On Oct 10, 2019, at 9:42 AM, Maciej Stachowiak wrote: > > For clarity, it’s already possible to render to a regular canvas offscreen. > The can be hidden using any of the techniques that can make any > other canvas invisible. Name notwithstanding, OffscreenCanvas is mainly about > being abl

Re: [webkit-dev] Implementing OffscreenCanvas

For clarity, it’s already possible to render to a regular canvas offscreen. The can be hidden using any of the techniques that can make any other canvas invisible. Name notwithstanding, OffscreenCanvas is mainly about being able to render from a Worker, not about enabling rendering offscreen.

Re: [webkit-dev] Implementing OffscreenCanvas

Hi John, I don't know what the current state is of counter-measures for such an attack, but I don't immediately imagine OffscreenCanvas would make them more effective. The patch series doesn't add any new rendering paths, so whatever was possible before will likely still be possible and whatever w

Re: [webkit-dev] Implementing OffscreenCanvas

Hi Chris! Canvas is a very popular GPU fingerprinting vector and allowing it offscreen sounds like a more convenient way to perform such an attack on user privacy. Do you know if Blink or Gecko have elaborated on this? What is your assessment? Given the cross-engine effort to fight device finge

[webkit-dev] Implementing OffscreenCanvas

Hi all, I've spent the last month or so 'finishing' the implementation of OffscreenCanvas[1], based on Žan Doberšek's work from a year ago[2]. OffscreenCanvas is an API for being able to use canvas drawing without a visible canvas, and from within Workers. It's supported by Blink and has partial s

[webkit-dev] Implementing requestIdleCallback

Hi all, I'm starting the effort to implement requestIdleCallback [1] in WebKit in https://bugs.webkit.org/show_bug.cgi?id=164193. It's an API for executing scripts when the browser is idle. It's supported by both Gecko & Blink as well as the old Edge engine. Because we don't plan on implementing

Re: [webkit-dev] Implementing MathML stylistic attributes in WebKit

On 02/09/2019 22:12, Ryosuke Niwa wrote: > > On Mon, Sep 2, 2019 at 7:11 AM Frédéric Wang > wrote: > > > Currently MathML attributes mathvariant, displaystyle and > scriptlevel [1] [2] are implemented in WebKit using custom "style > resolution" and "one-glyph r

Re: [webkit-dev] Implementing MathML stylistic attributes in WebKit

On Mon, Sep 2, 2019 at 7:11 AM Frédéric Wang wrote: > > Currently MathML attributes mathvariant, displaystyle and scriptlevel [1] > [2] are implemented in WebKit using custom "style resolution" and > "one-glyph rendering" inside the MathML layout code [3] [4] [5]. These > features involve text re

[webkit-dev] Implementing MathML stylistic attributes in WebKit

Hello, Currently MathML attributes mathvariant, displaystyle and scriptlevel [1] [2] are implemented in WebKit using custom "style resolution" and "one-glyph rendering" inside the MathML layout code [3] [4] [5]. These features involve text rendering and interaction with CSS font-size, so it is dif

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

In that case, I agree that it does not make much sense to implement the FIDO U2F API. I would definitely be interested in working on Web Authentication for WebKit. Rick - I think collaborating with people working on Chromium and Edge would be great. Thanks! - Jacob Greenfield > On Feb 22, 20

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

As I understand, there's active development going on in both chromium and Edge for Web Authentication right now. I'm sure those folks would love to collaborate with someone working in WebKit (and I'm happy to make introductions). On Wed, Feb 22, 2017 at 6:08 PM, Sam Weinig wrote: > > On Feb 22,

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

> On Feb 22, 2017, at 1:22 PM, Ryosuke Niwa wrote: > > On Wed, Feb 22, 2017 at 12:56 PM, Rick Byers > wrote: > Chrome ships with a built-in extension that exposes the high-level API (which > I think we all agree is a hack). We recently had this discussion >

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

On Wed, Feb 22, 2017 at 12:56 PM, Rick Byers wrote: > Chrome ships with a built-in extension that exposes the high-level API > (which I think we all agree is a hack). We recently had this discussion > > about the

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

Chrome ships with a built-in extension that exposes the high-level API (which I think we all agree is a hack). We recently had this discussion about the right path forward here, and agreed that we should instead fo

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

> On Feb 22, 2017, at 5:52 AM, Jacob Greenfield wrote: > > I’m working on adding support to WebKit for FIDO U2F (JS API: > https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-javascript-api-v1.1-id-20160915.html > Architecture overview: > https://fidoalliance.org/specs/fido-u2f-

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

On Wed, 2017-02-22 at 12:20 -0500, Jacob Greenfield wrote: > Michael, > > Thanks for the info. After looking into things a bit more - let me > know if this does not make sense - it looks like it may be better to > reimplement for WebKit. OK, your explanation sounds reasonable to me. Michael

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

Michael, Thanks for the info. After looking into things a bit more - let me know if this does not make sense - it looks like it may be better to reimplement for WebKit. Specifically, it looks like hidapi does some opaque stuff with threading that may leave idle threads around, to expose a consi

Re: [webkit-dev] Implementing Universal Second Factor (U2F)

On Wed, 2017-02-22 at 08:52 -0500, Jacob Greenfield wrote: > The (USB) protocol itself works by sending USB HID reports (packets) > to the key and getting USB HID reports back. There is a reference > implementation by one of the members of the specification group - > libu2f-host (by Yubico); howeve

[webkit-dev] Implementing Universal Second Factor (U2F)

I’m working on adding support to WebKit for FIDO U2F (JS API: https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-javascript-api-v1.1-id-20160915.html Architecture overview: https://fidoalliance.org/specs/fido-u2f-v1.1-id-20160915/fido-u2f-overview-v1.1-id-20160915.html ). The FID

Re: [webkit-dev] Implementing slot-based shadow DOM API

Hi all, Antti and I have successfully implemented new slot-based shadow DOM API, and it has been enabled on Safari Technology Preview as well as Safari 10 included in macOS Sierra. There are a few remaining bugs to be fixed as tracked in webkit.org/b/148695 but we believe we've polished it enough

Re: [webkit-dev] Implementing Web Animations

On 6 Nov 2015, at 3:22 am, Darin Adler wrote: >> On Nov 4, 2015, at 6:19 PM, Nikos Andronikos >> wrote: >> >> The current plan, after chatting to Dean at TPAC, will be to implement the >> web animations model as a new module, with a runtime flag for switching CSS >> and SVG animations over t

Re: [webkit-dev] Implementing Web Animations

> On Nov 4, 2015, at 6:19 PM, Nikos Andronikos > wrote: > > The current plan, after chatting to Dean at TPAC, will be to implement the > web animations model as a new module, with a runtime flag for switching CSS > and SVG animations over to use the new model. We should have a goal to have th

[webkit-dev] Implementing Web Animations

Hi all, Myself and a colleague are going to make a start on implementing Web Animations. The current plan, after chatting to Dean at TPAC, will be to implement the web animations model as a new module, with a runtime flag for switching CSS and SVG animations over to use the new model. After re

[webkit-dev] Implementing slot-based shadow DOM API

Hi all, Now that our Slot Proposal [1] has been accepted by the Web Apps WG in the latest editor's working draft of shadow DOM API [2], I've started implementing in WebKit. You can follow this effort on Bugzilla [3]. The feature will be enabled by default without prefix on trunk on Mac and iOS po

[webkit-dev] Implementing DragEvent and move MouseEvent.dataTransfer to DragEvent

Hi webkit-devI would like to implement DragEvent and move MouseEvent.dataTransfer to DragEvent. Such is the spec: https://html.spec.whatwg.org/multipage/interaction.html#dragevent Gecko and Chromium already has the DragEvent interface and has the dataTransfer attribute only on that interface.

[webkit-dev] Implementing CSS "will-change"

I intend to implement the CSS will-change property, as specified here: http://www.w3.org/TR/css-will-change-1/ Since this is already supported unperfected by Firefox and Chrome, I will implement it unprefixed, and without an ENABLE flag. Work will be d

[webkit-dev] Implementing Media Session API

Hi WebKit Developers! I plan on implementing the Media Session API in WebKit. The Media Session API provides web developers the ability to respond to media keys on hardware such as keyboards and remote controls. The tentative spec can be found here: https://mediasession.spec.whatwg.org

Re: [webkit-dev] Implementing ES6 class syntax in JSC

So awesome, Ryosuke! It's good to see this rolling. On Mon, Mar 16, 2015 at 10:59 PM, Ryosuke Niwa wrote: > Hi all, > > The feature has been enabled by default in > https://trac.webkit.org/changeset/181618. Please try it out and file bugs > under 140491 and cc me. > > - R. Niwa > > > ___

Re: [webkit-dev] Implementing ES6 class syntax in JSC

Hi all, The feature has been enabled by default in https://trac.webkit.org/changeset/181618. Please try it out and file bugs under 140491 and cc me. - R. Niwa ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/list

[webkit-dev] Implementing ES6 class syntax in JSC

Hello WebKittens, I'm implementing ES6 class syntax behind a build flag in https://webkit.org/b/140491. Please let me know if you have any concerns or comments. - R. Niwa ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/

Re: [webkit-dev] Implementing object-fit

Yes, I don’t expect much or any spec churn, especially since Opera shipped this (prefixed) for several years. Simon On Aug 26, 2013, at 5:46 PM, Maciej Stachowiak wrote: > > Is the implementation likely to be correct enough that we wouldn't risk > locking in buggy behavior? > > - Maciej >

Re: [webkit-dev] Implementing object-fit

Is the implementation likely to be correct enough that we wouldn't risk locking in buggy behavior? - Maciej On Aug 26, 2013, at 4:23 PM, Simon Fraser wrote: > Support for CSS object-fit has landed in Blink (runtime-enabled)[1] and I’d > like to land it in WebKit[2]. > > The spec[3] is at C

Re: [webkit-dev] Implementing object-fit

Sounds fine to me. -Sam On Aug 26, 2013, at 4:23 PM, Simon Fraser wrote: > Support for CSS object-fit has landed in Blink (runtime-enabled)[1] and I’d > like to land it in WebKit[2]. > > The spec[3] is at CR, so I’d like to land this unprefixed, and not protected > by ENABLE guards. Does any

[webkit-dev] Implementing object-fit

Support for CSS object-fit has landed in Blink (runtime-enabled)[1] and I’d like to land it in WebKit[2]. The spec[3] is at CR, so I’d like to land this unprefixed, and not protected by ENABLE guards. Does anyone see fit to object? Simon [1] http://src.chromium.org/viewvc/blink?view=revision&r

Re: [webkit-dev] Implementing Webform UI controls like datepicker/coloricker widget with shadowDOM

Why do we want to do that? And why are we starting a new thread after morrita's response on http://lists.webkit.org/pipermail/webkit-dev/2013-January/023334.html ? On Fri, Jan 18, 2013 at 9:55 AM, Hema Chidanand wrote: > Hi webkit-dev, > > This is a thought to have the webform UI modal controls w

Re: [webkit-dev] Implementing Complex webform Widgets using ShadowDom

Dear Morrita, as per your suggestion i have filed a bug at https://bugs.webkit.org/show_bug.cgi?id=107296. I shall be very thankful to recieve your comments on the same. Thanks On Tue, Jan 15, 2013 at 10:39 AM, Hajime Morrita wrote: > Hi Hema, > > If you are talking about WebKit and HTML, it a

[webkit-dev] Implementing Webform UI controls like datepicker/coloricker widget with shadowDOM

Hi webkit-dev, This is a thought to have the webform UI modal controls widgets , platform independent with shadow DOM . See: https://bugs.webkit.org/show_bug.cgi?id=107296 kindly provide with the comments and suggestions on the same. Regards, Hema. ___

Re: [webkit-dev] Implementing Complex webform Widgets using ShadowDom

Hi Hema, If you are talking about WebKit and HTML, it already does it for some of its built-in HTML elements. Some UI controls, which are modal and don't fit into the page layout, are implemented using native UI controls. These modal controls shouldn't constrained by WebKit rendering area like if

[webkit-dev] Implementing Complex webform Widgets using ShadowDom

Hi All, What is your view in Implemeting Complex webform widgets like CalendarPicker Widget , Colorpicker widget using ShadowDom . May i know the pro's and con's ? How to start off with it. Thanks & Regards, Hema. ___ webkit-dev mailing list webkit-dev@

Re: [webkit-dev] Implementing rendering support for -webkit-text-decoration-skip

  On November 1, 2012 at 6:51 PM Lamarque Souza wrote: >   > > Hi all, > >   > > > I am trying to implement https://bugs.webkit.org/show_bug.cgi?id=92801 > "[css3-text] Add support for -webkit-text-decoration-skip" and have some > doubts about the best way to do it for all parsed values

[webkit-dev] Implementing rendering support for -webkit-text-decoration-skip

  Hi all,   I am trying to implement https://bugs.webkit.org/show_bug.cgi?id=92801 "[css3-text] Add support for -webkit-text-decoration-skip" and have some doubts about the best way to do it for all parsed values for -webkit-text-decoration-skip (objects, spaces, ink) [1] The attached patch

Re: [webkit-dev] Implementing CSS3 Paged Media Margin Boxes

On Tuesday 01 May 2012 11:16:07 Simon Fraser wrote: > Dave Hyatt is interested in doing more Paged Media stuff. > > Any work in this area should be preceded by a conversation with Dave. OK, thanks. I've send him an email and await input from him. Cheers > On Apr 27, 2012, at 11:47 AM, Eric Seid

Re: [webkit-dev] Implementing CSS3 Paged Media Margin Boxes

Dave Hyatt is interested in doing more Paged Media stuff. Any work in this area should be preceded by a conversation with Dave. Simon On Apr 27, 2012, at 11:47 AM, Eric Seidel wrote: > Ref-tests did not exist in WebKit when I last looked at this. I added > pdf printing tests, only to realize t

Re: [webkit-dev] Implementing CSS3 Paged Media Margin Boxes

Ref-tests did not exist in WebKit when I last looked at this. I added pdf printing tests, only to realize that pdfs include user/machine information and thus are useless for x-machine testing. If our ref-test mechanism works for large pages that could work well. :) With printing tests you'll wan

Re: [webkit-dev] Implementing CSS3 Paged Media Margin Boxes

On Friday 27 April 2012 10:08:13 Eric Seidel wrote: > When I last looked at the page media stuff (long ago). The problem > was mostly going to be testing. We don't have a good way to do > printing tests right now in WebKit. Someone in the webkit community introduced me to the idea of reftests, w

Re: [webkit-dev] Implementing CSS3 Paged Media Margin Boxes

When I last looked at the page media stuff (long ago). The problem was mostly going to be testing. We don't have a good way to do printing tests right now in WebKit. On Fri, Apr 27, 2012 at 7:22 AM, Milian Wolff wrote: > Hey all, > > I would like to work on the CSS3 Paged Media support, esp. th

[webkit-dev] Implementing CSS3 Paged Media Margin Boxes

Hey all, I would like to work on the CSS3 Paged Media support, esp. the margin boxes. I'm studying the code for some time now and would welcome it if someone could assist me in figuring out what needs to be done... First up, I think I should tackle the missing support in the parser, i.e. solvi

Re: [webkit-dev] Implementing the Speech JavaScript API

On Thu, Mar 1, 2012 at 20:49, Satish Sampath wrote: > Hi Adam, > > The proposal is to implement [3] which is a pure JS API and no new html > markup. Yes, what Satish said. My apologies for being a bit unclear about which one we plan implement. I have been following the ongoing refactoring work,

Re: [webkit-dev] Implementing the Speech JavaScript API

Hi Adam, Hi Adam, The proposal is to implement [3] which is a pure JS API and no new html markup. It will be implemented as a module as you suggested. The first patch in [4] shows the first iteration of the implementation ( https://bugs.webkit.org/attachment.cgi?id=129679&action=review ), though

Re: [webkit-dev] Implementing the Speech JavaScript API

Hi Hans, On Thu, Mar 1, 2012 at 4:17 AM, Hans Wennborg wrote: > Currently, there is some limited support for speech recognition in > WebKit, by means of the x-webkit-speech attribute to input elements. > We would like to continue the development of this to allow web apps to > better utilize the p

[webkit-dev] Implementing the Speech JavaScript API

Hello WebKit, Currently, there is some limited support for speech recognition in WebKit, by means of the x-webkit-speech attribute to input elements. We would like to continue the development of this to allow web apps to better utilize the possibilities of speech recognition and text-to-speech syn

Re: [webkit-dev] Implementing Shadow DOM spec in WebKit

Hi Dmitry, As you mention in your email, Adobe is interested in the Shadow DOM effort and we will coordinate with you to understand better how/if/where we can contribute. Good luck with both the implementation and the standards work! Kind regards, Vincent. Dmitry wrote: Hi WebKit! I wanted to

Re: [webkit-dev] Implementing Shadow DOM spec in WebKit

Hey Dmitri, Very awesome, great progress! Sencha is very interested in Web Components and we'll be giving you feedback and contribute help in any way we can. It (sadly) didn't make our 2012 Top 10 Wish List (I think it was a matter of timing), but it did receive mentions. Cheers, Jarred On Wed

Re: [webkit-dev] Implementing Shadow DOM spec in WebKit

On Wed, Jan 11, 2012 at 3:56 PM, Maciej Stachowiak wrote: > > Hi Dmitri! > > I remember last time this came up, there was some controversy, both within > the WebKit community and among browser implementors more broadly. Kudos for > writing a much more comprehensive spec and taking more of the fe

Re: [webkit-dev] Implementing Shadow DOM spec in WebKit

Hi Dmitri! I remember last time this came up, there was some controversy, both within the WebKit community and among browser implementors more broadly. Kudos for writing a much more comprehensive spec and taking more of the feedback into account. For example, I am delighted to see that there i

[webkit-dev] Implementing Shadow DOM spec in WebKit

Hi WebKit! I wanted to let you know that we are planning to implement the Shadow DOM specification (http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html) in WebKit. For now, its public-facing APIs will hide behind ENABLE(SHADOW_DOM) flag and help gather implementer and developer

Re: [webkit-dev] Implementing

On Wed, Sep 14, 2011 at 1:26 AM, Roland Steiner wrote: > On Mon, Sep 12, 2011 at 4:21 PM, Dimitri Glazkov wrote: > >> Yeah. You're right. We should get Hixie to change the spec. I don't >> think we should implement currently spec'd behavior or change the >> name. That last option sounds exceptiona

Re: [webkit-dev] Implementing HTML5 time element

On Thu, 15 Sep 2011, Vineet Chaudhary wrote: > > I am intending to implement the HTML5 tag. Could you elaborate on what your use case is? The reason I ask is that we are thinking of dropping from the spec. If there's a good reason to keep it, that would be good to know. > With Reference to S

Re: [webkit-dev] Implementing HTML5 time element

The biggest question for me for this feature is what locale-specific formatting we plan for these dates and times. Will we be adding more code to the WebCore platform layer to do this? Will we use locale-specific formatting code already present in JavaScriptCore, perhaps moving it to WTF for the

[webkit-dev] Implementing HTML5 time element

Hi, I am intending to implement the HTML5 tag. With Reference to Specification on : http://www.w3.org/TR/html5/text-level-semantics.html#the-time-element - I have already logged bug for this in webkit bugzilla https://bugs.webkit.org/show_bug.cgi?id=68156 Description : The time element represe

Re: [webkit-dev] Implementing

On Mon, Sep 12, 2011 at 4:21 PM, Dimitri Glazkov wrote: > Yeah. You're right. We should get Hixie to change the spec. I don't > think we should implement currently spec'd behavior or change the > name. That last option sounds exceptionally bad. Roland, can you post > on that thread and request the

Re: [webkit-dev] Implementing

On Mon, Sep 12, 2011 at 4:11 PM, Maciej Stachowiak wrote: > > On Sep 8, 2011, at 2:28 PM, Roland Steiner wrote: > > Hi all, > After several discussions on the whatwg@ mailing list and others, we would > like to go forward with adding

Re: [webkit-dev] Implementing

On Sep 8, 2011, at 2:28 PM, Roland Steiner wrote: > Hi all, > > After several discussions on the whatwg@ mailing list and others, we would > like to go forward with adding

Re: [webkit-dev] Implementing

Ryosuke Niwa wrote: >>> Why do diverge? It seems like we should at least prefix the >>> attribute with webkit in the case spec changes in the future. > >> See above linked discussion for details. In the end we felt limiting >> the selector matching to the scope is more natural, and - with the >> p

Re: [webkit-dev] Implementing

On Fri, Sep 9, 2011 at 12:51 PM, Roland Steiner wrote: > On Thu, Sep 8, 2011 at 6:51 PM, Ryosuke Niwa wrote: > >> Very excited for this feature! >> >> On Thu, Sep 8, 2011 at 2:28 PM, Roland Steiner < >> rolandstei...@chromium.org> wrote: >>> >>> As per discussion on >>> http://lists.whatwg.org/pi

Re: [webkit-dev] Implementing

On Thu, Sep 8, 2011 at 6:51 PM, Ryosuke Niwa wrote: > Very excited for this feature! > > On Thu, Sep 8, 2011 at 2:28 PM, Roland Steiner > wrote: >> >> As per discussion on >> http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/032056.html, >> our implementation would diverge from the c

Re: [webkit-dev] Implementing

On Fri, Sep 9, 2011 at 12:28 AM, Roland Steiner wrote: > > ad 3.) Implementation of scoped selector matching works as follows: > > .) scoped style sheet rules are contained in a separate map element address> -> RuleSet > .) add a field to ParentStackFrame that identifies the > closest ParentStack

Re: [webkit-dev] Implementing

Very excited for this feature! On Thu, Sep 8, 2011 at 2:28 PM, Roland Steiner wrote: > > As per discussion on > http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/032056.html, > our implementation would diverge from the current HTML5 spec > Why do diverge? It seems like we should at le

[webkit-dev] Implementing

Hi all, After several discussions on the whatwg@ mailing list and others, we would like to go forward with adding to WebKit. Overview: Style rules within