- From: Peter Linss <notifications@github.com>
- Date: Tue, 29 Oct 2024 15:35:09 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 29 October 2024 22:35:13 UTC
A concern about whatever mechanism is used here is that there is an existing behavior of copy-on-write behavior when the same stylesheet is loaded from multiple places. e.g. if I `<link>` a.css twice, there's one instanace in RAM, but if it's modified via CSSOM, it splits into two instances so page authors can't tell it was shared in the first place. However, with stylesheets that are adopted via JS API, the same instance is re-used and changes to that instance are reflected in each place they are referenced. At the least we need to be clear what the expected behavior will be when declaratively adopting a stylesheet. It's also worth thinking about either reconciling the behavior or giving authors explicit mechanisms to opt-in to the behavior they desire. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1000#issuecomment-2445449878 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1000/2445449878@github.com>
Received on Tuesday, 29 October 2024 22:35:13 UTC