Nope - no concerns from me.
On 7/3/25 3:11 a.m., Marja Hölttä wrote:
Thanks for looking into it! Unfortunately we don't have a range of
milestones now, so I'll need to come back to this thread when we have.
By sending this request early we were hoping that if there are any
concerns or action items to do before getting the approval, we'd get
to know about them early, and when our partner is ready we'd be also
ready to start the experiment. Please let me know if there are any
such concerns or action items currently known.
(I added a comment to the requests-for-position about the per-function
extension of this proposal.)
On Thu, Jun 5, 2025 at 2:36 PM Mike Taylor <miketa...@chromium.org> wrote:
On 6/5/25 8:17 AM, 'Marja Hölttä' via blink-dev wrote:
Contact emails
ma...@google.com
Explainer
https://github.com/WICG/explicit-javascript-compile-hints-file-based
Specification
There's no spec or draft spec for the per-function part yet -
getting feedback on the input format is one of the goals of the
Origin Trial.
Summary
Allow attaching information about which functions should be eager
parsed & compiled in JavaScript files.
The information will be encoded as magic comments.
This is an extension of the Per-File Explicit Compile Hints
feature ( https://chromestatus.com/feature/5100466238652416 ),
where we now allow marking individual functions for eager parsing
& compilation.
Blink component
Blink>JavaScript
TAG review
None
TAG review status
Pending
Risks
Interoperability and Compatibility
None
Gecko: N/A
(https://github.com/mozilla/standards-positions/issues/780) This
is a position request for the previous iteration of compile
hints; the per-file version. We expect their views about this
extension to be similar.
WebKit: N/A
(https://github.com/WebKit/standards-positions/issues/172) This
is a position request for the previous iteration of compile
hints; the per-file version. We expect their views about this
extension to be similar.
Non-blocking feedback: adding a comment about this proposal to
those existing issues seems good.
Web developers: Positive
- Microsoft is interested in prototyping; needs the Origin Trial
for evaluating performance in the wild
- General positive sentiment, e.g., TC39 tooling meeting
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs,
such that it has potentially high risk for Android WebView-based
applications?
None
Goals for experimentation
- Evaluate the performance improvement potential for real world
web apps
- Get feedback about the input format
Ongoing technical constraints
None
Debuggability
None
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
No
Is this feature fully tested by web-platform-tests?
No
Flag name on about://flags
None
Finch feature name
None
Non-finch justification
Web developers need to enable this feature on their side; adding
a Finch flag as an additional gate doesn't make sense.
Requires code in //chrome?
False
Estimated milestones
No milestones specified
(Will need to wait for partners to be ready to start the Origin
Trial)
We will need a range of milestones before approving. One of two
options might work for you:
1) You request 6 milestones now starting in MXXX (i.e., M140 to
M145), if you're reasonably confident your partners can be
experiment in that window.
2) You come back to the thread once you know which milestones you
are requesting and we can approve then.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5153430045458432?gate=6215402451107840
This intent message was generated by Chrome Platform Status.
--
Google Germany GmbH
Erika-Mann-Straße 33
80636 München
*
*
Geschäftsführer: Paul Manicle, Liana Sebastian.
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
*
*
Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise
erhalten haben sollten, leiten Sie diese bitte nicht an jemand
anderes weiter, löschen Sie alle Kopien und Anhänge davon und
lassen Sie mich bitte wissen, dass die E-Mail an die falsche
Person gesendet wurde.
This e-mail is confidential. If you received this communication
by mistake, please don't forward it to anyone else, please erase
all copies and attachments, and please let me know that it has
gone to the wrong person.
--
You received this message because you are subscribed to the
Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAED6dUAWhmj0jkb5Qt-JptbEN4ROoNRZW5SPRjFC%2B20XuXs8rw%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAED6dUAWhmj0jkb5Qt-JptbEN4ROoNRZW5SPRjFC%2B20XuXs8rw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
Google Germany GmbH
Erika-Mann-Straße 33
80636 München
*
*
Geschäftsführer: Paul Manicle, Liana Sebastian.
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
*
*
Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise
erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes
weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich
bitte wissen, dass die E-Mail an die falsche Person gesendet wurde.
This e-mail is confidential. If you received this communication by
mistake, please don't forward it to anyone else, please erase all
copies and attachments, and please let me know that it has gone to the
wrong person.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/de941183-5cd0-4630-aed1-be0579c552d1%40chromium.org.
