Bug 1598151 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Sebastian Zartner [:sebo] from comment #2)
> (In reply to Tom Ritter [:tjr] (sec-approvals paused until after release) from comment #1)
> > layout.css.motion-path-ray.enabled has been enabled in Nightly for several years at this point I believe...
> 
> Yes, but there are several open issues blocking shipping. I've added the ones I saw in the [main tracking bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1186329) now. Could be that there are others.
> Maybe Boris can decide how to proceed here.
> 
> Sebastian

Thanks for adding these dependencies. I didn't finish this because of the spec issue in Bug 1581237, and at that moment, only Gecko and Chrome implemented ray() function. However, it seems WebKit had implemented `ray()` last year, and so perhaps it's time to keep working on this (i.e. finish the dependencies and ship `ray()`). This is not in the backlog of layout team now, so I'd like to mention this in the layout meeting or my 1-on-1 with Frank.
(In reply to Sebastian Zartner [:sebo] from comment #2)
> (In reply to Tom Ritter [:tjr] (sec-approvals paused until after release) from comment #1)
> > layout.css.motion-path-ray.enabled has been enabled in Nightly for several years at this point I believe...
> 
> Yes, but there are several open issues blocking shipping. I've added the ones I saw in the [main tracking bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1186329) now. Could be that there are others.
> Maybe Boris can decide how to proceed here.
> 
> Sebastian

Thanks for adding these dependencies. I didn't finish this because of the spec issue in Bug 1581237, and at that moment, only Gecko and Chrome implemented ray() function (and I jumped to other topics). However, it seems WebKit had implemented `ray()` last year, and so perhaps it's time to keep working on this (i.e. finish the dependencies and ship `ray()`). This is not in the backlog of layout team now, so I'd like to mention this in the layout meeting or my 1-on-1 with Frank.
(In reply to Sebastian Zartner [:sebo] from comment #2)
> (In reply to Tom Ritter [:tjr] (sec-approvals paused until after release) from comment #1)
> > layout.css.motion-path-ray.enabled has been enabled in Nightly for several years at this point I believe...
> 
> Yes, but there are several open issues blocking shipping. I've added the ones I saw in the [main tracking bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1186329) now. Could be that there are others.
> Maybe Boris can decide how to proceed here.
> 
> Sebastian

Thanks for adding these dependencies. I didn't finish this because of the spec issue in Bug 1581237, and at that moment, only Gecko and Chrome implemented ray() function (and I jumped to other topics). However, it seems WebKit had implemented `ray()` last year [WebKit Bug 233153](https://bugs.webkit.org/show_bug.cgi?id=233153), and so perhaps it's time to keep working on this (i.e. finish the dependencies and ship `ray()`). This is not in the backlog of layout team now, so I'd like to mention this in the layout meeting or my 1-on-1 with Frank.
(In reply to Sebastian Zartner [:sebo] from comment #2)
> (In reply to Tom Ritter [:tjr] (sec-approvals paused until after release) from comment #1)
> > layout.css.motion-path-ray.enabled has been enabled in Nightly for several years at this point I believe...
> 
> Yes, but there are several open issues blocking shipping. I've added the ones I saw in the [main tracking bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1186329) now. Could be that there are others.
> Maybe Boris can decide how to proceed here.
> 
> Sebastian

Thanks for adding these dependencies. I didn't finish this because of the spec issue in Bug 1581237, and at that moment, only Gecko and Chrome implemented ray() function (and I jumped to other topics). However, it seems WebKit had implemented `ray()` last year ([WebKit Bug 233153](https://bugs.webkit.org/show_bug.cgi?id=233153)), and so perhaps it's time to keep working on this (i.e. finish the dependencies and ship `ray()`). This is not in the backlog of layout team now, so I'd like to mention this in the layout meeting or my 1-on-1 with Frank.

Back to Bug 1598151 Comment 3