Last modified: 2014-06-20 21:54:26 UTC
Various wikis use section=new on js or css pages in combination with "preload" and "editintro" to make it easier for non-developers to "install" a user script or style modification. For example on [[nl:User:Krinkle/RTRC]], https://nl.wikipedia.org/w/index.php?title=Gebruiker:Krinkle/RTRC&action=render, there is a link to: https://nl.wikipedia.org/w/index.php?title=Speciaal:Mypage/common.js&action=edit§ion=new&preload=User:Krinkle/install/RTRC&editintro=User:Krinkle/install-editintro But this results in the "sectioneditnotsupported-text" error message as of recently.
Looks like it is a more recent regression (not just regression from when ContentHandler was added) as it worked a few months ago when bug 43008 was raised and fixed.
The resolution of bug 43008 was to raise the "sectioneditnotsupported-text" error. See the implementation in https://gerrit.wikimedia.org/38689/ which added the error message.
Bump.
bump as I'm interested in this as well..
(In reply to Krinkle from comment #0) > Various wikis use section=new on js or css pages in combination with > "preload" and "editintro" to make it easier for non-developers to "install" > a user script or style modification. Is this a use case we wish to encourage? From my perspective this is a frightening thing to encourage. If there's popular JS/CSS things out there, a community should make it into a gadget (this is, after all, what they're for).
(In reply to James Forrester from comment #5) > (In reply to Krinkle from comment #0) > > Various wikis use section=new on js or css pages in combination with > > "preload" and "editintro" to make it easier for non-developers to "install" > > a user script or style modification. > > Is this a use case we wish to encourage? From my perspective this is a > frightening thing to encourage. If there's popular JS/CSS things out there, > a community should make it into a gadget (this is, after all, what they're > for). Not all userscripts are popular enough to become gadgets, and some of them (for example WikiProject specific scripts) should likely not be available as gadgets in most cases.
(In reply to Technical 13 from comment #6) > (In reply to James Forrester from comment #5) > > (In reply to Krinkle from comment #0) > > > Various wikis use section=new on js or css pages in combination with > > > "preload" and "editintro" to make it easier for non-developers to "install" > > > a user script or style modification. > > > > Is this a use case we wish to encourage? From my perspective this is a > > frightening thing to encourage. If there's popular JS/CSS things out there, > > a community should make it into a gadget (this is, after all, what they're > > for). > > Not all userscripts are popular enough to become gadgets, and some of them > (for example WikiProject specific scripts) should likely not be available as > gadgets in most cases. Isn't that more a reason to have better management/listing of gadgets than revert this intentional removal of functionality? (See bug 43008 comment 2).
That would be one of [[mw:Gadgets 3.0]] features: "Instead of scaring people with a huge list, provide a selection UI with category-based browsing " Unfortunately we are not even on 2.0 yet...
