--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b2280099-f9a5-46db-b951-e380728b1bbfo%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9yOznCKQmARoMznuhaq5EdMjF0pYxTx5BF%2BZg0DSSKjA%40mail.gmail.com.
OK. I will send a PSA about openOrClosedShadowRoot API before landing CL.Thanks to kent-san and Chris.Regards,Miyoung Shin2020년 8월 4일 화요일 오전 9시 53분 1초 UTC+9, Kent Tamura 님의 말:
I think we had better send a PSA about the API change before landing CLs. Adding new IDL attributes/functions to a web-exposed interface might affect future enhancements on the interface even if the new IDL attributes/functions are exposed only to the extension context.For example, we would have troubles if a standard added a web-exposed openOrClosedShadowRoot and it's not compatible with the extension-only openOrClosedShadowRoot. We could suggest to rename it if we knew the extension-only openOrClosedShadowRoot.
On Fri, Jul 31, 2020 at 9:05 AM Chris Harrelson <chri...@chromium.org> wrote:
Hi,If openOrClosedShadowRoot will only be exposed to scripts that are in Chrome Extensions, and not a regular web page, then no you don't need an intent-to-ship. We don't consider extensions to be part of the official web platform.Thanks for asking,Chris
On Thu, Jul 30, 2020 at 4:50 PM <myid...@igalia.com> wrote:
--Hi, all,I'm working on adding Element.openOrClosedShadowRoot to allow access to closed shadow roots from Extensions[1]. As discussed in the bug[2], we referred to openOrClosedShadowRoot already supported by Mozilla[3]. I would like to hear your opinion on whether intent-to-ship is necessary for this case, although it will not be exposed to the general Web API, but only to Extensions.Thanks,Miyoung Shin
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 blin...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b2280099-f9a5-46db-b951-e380728b1bbfo%40chromium.org.
--
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 blin...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9yOznCKQmARoMznuhaq5EdMjF0pYxTx5BF%2BZg0DSSKjA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BN6QZvHoVsO37dsH8gkuMhw014oz32HD_o1PUOfaf8RJJA86Q%40mail.gmail.com.
I think we had better send a PSA about the API change before landing CLs. Adding new IDL attributes/functions to a web-exposed interface might affect future enhancements on the interface even if the new IDL attributes/functions are exposed only to the extension context.
For example, we would have troubles if a standard added a web-exposed openOrClosedShadowRoot and it's not compatible with the extension-only openOrClosedShadowRoot. We could suggest to rename it if we knew the extension-only openOrClosedShadowRoot.
On Fri, Jul 31, 2020 at 9:05 AM Chris Harrelson <chri...@chromium.org> wrote:
Hi,If openOrClosedShadowRoot will only be exposed to scripts that are in Chrome Extensions, and not a regular web page, then no you don't need an intent-to-ship. We don't consider extensions to be part of the official web platform.Thanks for asking,Chris
On Thu, Jul 30, 2020 at 4:50 PM <myid...@igalia.com> wrote:
--Hi, all,I'm working on adding Element.openOrClosedShadowRoot to allow access to closed shadow roots from Extensions[1]. As discussed in the bug[2], we referred to openOrClosedShadowRoot already supported by Mozilla[3]. I would like to hear your opinion on whether intent-to-ship is necessary for this case, although it will not be exposed to the general Web API, but only to Extensions.Thanks,Miyoung Shin
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 blin...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b2280099-f9a5-46db-b951-e380728b1bbfo%40chromium.org.
--
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 blin...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9yOznCKQmARoMznuhaq5EdMjF0pYxTx5BF%2BZg0DSSKjA%40mail.gmail.com.
- We need to implement an infrastructure to expose Web APIs to extensions only. This is a technically solvable problem but will be an amount of work / complexity in the binding layer.
- The current policy is that extension APIs are added to the chrome.* namespace in a way that doesn't pollute web-exposed APIs.Is there any reason you cannot go with the chrome.* namespace like other extension APIs?
> - We need to implement an infrastructure to expose Web APIs to extensions only. This is a technically solvable problem but will be an amount of work / complexity in the binding layer.
I've updated the binding script to introduce ExposedPerWorld=MainWorld|IsolatedWorld for the attribute only(not method & interface) at a CL[1]. If we need to expand it for method & interface or add test cases, I'm willing to proceed in a follow-up CL. Currently, I need to get a review from the reviewer to see if CL is properly approached, but if there are the extra things I can contribute, I would like to do it.
There was this discussion at the bug[2][3], and I guess it could answer your question. (+rdevlin.cronin@)
[1] https://crrev.com/c/2319951
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=778816#c10
[3] https://bugs.chromium.org/p/chromium/issues/detail?id=778816#c18
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b7b646af-c9f2-4362-b452-823c25f055ffo%40chromium.org.
If we'd introduce Element.prototype.openOrClosedShadowRoot, I think we'd need an agreement among browser vendors?
The issue here is that, by exposing this to extensions by modifying Element.prototype in extensions, you are impacting future standardization efforts on the web platform.