Basically, if you are ok with it only taking affect after page load (so users see first the original page then the new version) it is trivial. However flash of wrongly styled content is a really bad user experience.
To do it without the flash of wrong version of toggle, is difficult due to the way our infrastructure is currently setup. Nothing insurmountable in principle, but high effort and involves some tradeoffs that seems not worth it in context. -- Brian p.s. for the avoidance of doubt, this is my personal opinion and not an "official" answer in any capacity. On Friday, September 30, 2022, Samuel Klein <meta...@gmail.com> wrote: > Dear WT, > > The perennial discussion about ways to provide logged-out users with > persistent customization of their reading experience in the browser has > cropped up again in the context of the pending deployment of Vector 2022. > > Can a cookie-based width toggle > <https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Deployment_of_Vector_(2022)#Alt_proposal:_gradual_changeover_+_width_toggle> > be offered without splitting the cache or otherwise making the toggler > regret their tog? > > The answers currently range from "*shouldn't be very complicated or > hacky, just toggling a class*..." and "*can be delivered to logged-out > users on top of the cached parser output*.." to "*impossible*". > > Could someone clarify the challenges and costs of trying to toggle css > classes in this way? > > Warmly, SJ > > -- > Samuel Klein @metasj w:user:sj +1 617 529 4266 >
_______________________________________________ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
