Timeline for 2023 DOM Changelog for Userscript Community
Current License: CC BY-SA 4.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2023 at 10:50 | comment | added | gcasar Staff |
@ShadowWizardIsSadAndAngry The original entry was related to our color change efforts (related post) but that was achieved without it. I've gone and reworded my original edit to hopefully keep it in line with the spirit of the post - to give folks a heads up that post-tags are special and have a higher likelihood to break user scripts in the future, even if we cannot provide a timeline around it. Realistically, this might still come up, but in smaller chunks.
|
|
| Dec 8, 2023 at 10:42 | history | edited | gcasarStaff | CC BY-SA 4.0 |
reintroduce `post-tag` to `s-tag` to highlight a likely breaking change
|
| Dec 7, 2023 at 10:54 | comment | added | Shadow Wizard | @gcasar the removed change, that was already planned, is officially aborted, or postponed to unknown time? (Also, in my opinion better keep it written here and add comment saying it's aborted or postponed, no?) | |
| Dec 7, 2023 at 10:42 | history | edited | gcasarStaff | CC BY-SA 4.0 |
removing post-tag
|
| Oct 9, 2023 at 9:39 | history | edited | gcasarStaff | CC BY-SA 4.0 |
further postponing the post-tag to s-tag migration
|
| Sep 29, 2023 at 9:22 | history | edited | gcasarStaff | CC BY-SA 4.0 |
postponed `s-tag` migration by a week to also include `js-post-tag`
|
| Sep 26, 2023 at 16:16 | history | edited | KyleMitStaffMod | CC BY-SA 4.0 |
added 11 characters in body
|
| Sep 26, 2023 at 16:07 | history | edited | gcasarStaff | CC BY-SA 4.0 |
include post-tag to s-tag (near-future) change
|
| Feb 9, 2023 at 19:36 | comment | added | KyleMit StaffMod | Hey @double-beep, had a quick discussion internally about this and we're not quite in easy "rollback" territory since this was a intentional move to refactor to an external icon package in order to not maintain the property list in two places - which always required two separate PRs to add icons. Added to the changelog with a workaround to use unkpg to get icons - which is the same package we're building from internally, so guaranteed to be the same. Thanks for pointing out and hopefully this helps | |
| Feb 9, 2023 at 19:33 | history | edited | KyleMitStaffMod | CC BY-SA 4.0 |
added notes about icons
|
| Feb 9, 2023 at 19:22 | comment | added | KyleMit StaffMod | @double-beep, ah, yeah, I see the PR - one previous to the one I was looking at. Looking into it. We refactored it to an imported method because our long term goal in is to not rely on global scope in scripts. But also want to see if we can produce an artifact on the global scope. | |
| Feb 9, 2023 at 19:02 | comment | added | double-beep |
@KyleMit the list used to be much longer (200+ icons). For example. Svg.Gear() and Svg.Eye() are missing.
|
|
| Feb 9, 2023 at 18:31 | comment | added | KyleMit StaffMod |
@double-beep, we recently did swap out our svg icons to point to StackExchange/Stacks-Icons, but I'm not sure that impacted the windows.Svg object got touched (It's possible though). We still have some icons explicitly wrapped as properties. Do you know what you're missing?
|
|
| Feb 9, 2023 at 18:05 | comment | added | double-beep |
It seems that somple properties of the global Svg object are now not exposed. Is this intentional?
|
|
| Feb 6, 2023 at 14:26 | vote | accept | KyleMitStaffMod | ||
| Feb 6, 2023 at 14:26 | history | made wiki | Post Made Community Wiki by KyleMitStaffMod | ||
| Feb 4, 2023 at 7:51 | comment | added | 0Valt | @StephenOstermiller to add to what's been said above, it's a well-known naming convention for CSS classes that are used by JS logic to match elements rather than to style things. | |
| Feb 3, 2023 at 21:44 | comment | added | KyleMit StaffMod | I share the sentiment and goal @SonictheAnonymousHedgehog, and hopefully we can provide some degree of lead time, but PRs sitting in the queue for 6-8 days is gonna really hurt in a 2 wk sprint cycle. Most of these are updated under the "clean beach principle" while working on a related ticket. | |
| Feb 3, 2023 at 20:38 | comment | added | Sonic the Anonymous Hedgehog | Just a word of advice, I'd highly recommend publishing advance notice when doing so, which can most easily be done when pushing the change into source control before the build deploys to the public sites, but preferably a few days' notice. This way, script authors can update their scripts so there's no downtime for script users. Some user scripts are important for content curation so having them be broken for 6-8 days while waiting for the script author to update it can be annoying. (A similar thing is already done today for translations.) | |
| Feb 3, 2023 at 20:33 | comment | added | KyleMit StaffMod |
We use that to distinguish that the only layer that should care about this class is JS to add event listeners / dom manipulation or something. This makes it easier to reason about changing the styles of something like .comment-active, knowing changing the class won't break any JavaScript.
|
|
| Feb 3, 2023 at 20:33 | comment | added | Kyle Pollard StaffMod | @StephenOstermiller stackoverflow.design/product/guidelines/javascript/… | |
| Feb 3, 2023 at 20:32 | comment | added | Stephen Ostermiller |
Out of curiosity, why would css classes start with js-?
|
|
| Feb 3, 2023 at 20:24 | history | edited | KyleMitStaffMod | CC BY-SA 4.0 |
Used non-breaking hyphen `‑` so dates don't wrap awkwardly in first column
|
| Feb 3, 2023 at 20:14 | history | answered | KyleMitStaffMod | CC BY-SA 4.0 |
