![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
Archive 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 | Archive 7 |
We still get requests like this once in a while, so I think turning Sharebox into a WP:Gadget may be a good idea. Personally I strongly dislike Facebook, but that is just my POV. Arcandam ( talk) 01:47, 23 May 2012 (UTC)
This has already been suggested four years ago, I wonder why it hasn't been added as a gadget. I've been using this script now for several months, and it is simply amazing. Very, very helpful. -- bender235 ( talk) 18:49, 7 June 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The AFC Helper Script ( code) is heavily used in reviewing by WikiProject Articles for creation. It is tested and works in all major browsers (Chrome, Firefox, IE, Opera, Safari) and skins (Monobook, Vector, Modern), and can be used by members of all user groups (except for creating submissions, which is only possible by autoconfirmed, nor on protected or title-blacklisted pages (obviously)). In its three-year history, it has grown to something beyond a simple script by Tim; it is now actively maintained by multiple users, including Mabdul, Excirial, and I. I believe that making this script a gadget would invite more users to participate in a project that is currently suffering from a massive backlog (see various talk page threads: Time to invite new users!, Backlog too large, Backlog is only going to get worse.), since prospective reviewers do not need to learn the complicated parameters for {{ AFC submission}} nor do they need to muddle in their userspace Javascript. It will also make the project known to those who are unaware of its existence. Thanks. — The Earwig (talk) 23:33, 23 June 2012 (UTC)
I think we are done here, right? Who can we ask to implement it? Arcandam ( talk) 14:04, 1 July 2012 (UTC)
Remember that watchlist RfC? It established that highlighting of unwatched changes should be off by default, but that an option should be available to enable it in preferences. Therefore, I would like to ask that two gadgets be enabled using the CSS at WP:CUSTOMWATCH: one enabling bold styling for unwatched changes, and one enabling an underscore (these received the most support in the RfC). Also, could you put a link to WP:CUSTOMWATCH—in case they want to make changes that aren't one of the gadgets—in the description of the gadgets? Thanks, David 1217 What I've done 15:01, 6 July 2012 (UTC)
See https://bugzilla.wikimedia.org - It has a link for advanced search ( Special:Search) in the sidebar. Is there any reason this link can not be added to the Wikipedia sidebar? This would allow people to do searches in a new browser tab without covering the current page.
Can a gadget allow one to place this link in the sidebar? -- Timeshifter ( talk) 10:56, 7 July 2012 (UTC)
All users have a gadget enabled by default for asking questions at Wikipedia:Teahouse, hence the smooth question box that pops up there. After some talk of adding another gadget for responding to existing questions, I'd written a script for that purpose, which I understand several editors have been using for a while, including some Foundation people. I wonder if someone could have a look into the possibility of enabling this too as a default gadget.
The aim of this script is to make it easier for new users to respond to these discussions, when they don't necessarily understand that this entails editing the section. Once in a while, people actually ask how to post a response. The script is based on the Ask gadget, and uses a similar input box, for uniformity. Equazcion (talk) 14:56, 10 Aug 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I would like to propose adding a new gadget, which would be enabled by default. This is based on Andrew's #Teahouse gadget discussed above, but more flexible and with some slight changes in behaviour. Basically wherever the template {{ commentr}} is used, it creates a link which pops up a small form. This can be used to leave a message, which is saved as a new section either on the current page or on a page specified as a template parameter. If JavaScript is not available, or the browser's implementation is FUBAR (glares at Internet Explorer 6), then the link will just go to the standard edit form.
The initial use case for this will be part of my Help Project fellowship. The idea is to place this template on certain important help pages, and collect feedback in a centralised location such as Wikipedia:Help Project/Feedback for attention and action by Help Project members. Since many of the people using the Help pages are not experienced Wikipedians, having a simple popup form without the complexities of the standard editing form will be better for them. In creating this gadget I've attempted to make it fairly flexible, so that it can be adopted for other projects in future if desired. The text and style of the form are all customisable by using template parameters.
I've tested in most major browsers (Chrome, Firefox, IE 7+, Safari), and apart from the above mentioned IE6 problem didn't see any issues. If people want to see the code it's currently at User:The wub/commentr.js and User:The wub/commentr.css, and if you wish to test you can add the following to Special:MyPage/common.js:
importScript( 'User:The wub/commentr.js' );
importStylesheet( 'User:The wub/commentr.css' );
If there are no problems or objections, I'd like to go ahead and enable this next week. the wub "?!" 12:54, 17 June 2012 (UTC)
once they ... click Save they get dumped to a different page from the one they were looking at- how so? -- Redrose64 ( talk) 20:58, 19 June 2012 (UTC)
The standard editing form has a lot of features that are important for normal editing of the encyclopediaI was under the impression that you were discussing the regular Edit tab, or a section's [edit] link. Upon hitting "Save page", those take you back where you came from. -- Redrose64 ( talk) 12:05, 20 June 2012 (UTC)
I would oppose adding such a gadget based upon the idea that it would be enabled by default. -- Nouniquenames ( talk) 04:48, 24 June 2012 (UTC)
As suggested by Arcandam, I have added this to the gadgets list for people to test, although it is not yet enabled by default. the wub "?!" 21:18, 24 June 2012 (UTC)
Comment as the instigator and creator (with significant help) of the current {{ Leave feedback}} system, I have some comments.
Since this page is for proposing addition of gadgets, I posted a pair of removal proposals at Wikipedia talk:Gadget#Deprecate textareasansserif? and Wikipedia talk:Gadget#Does Gadget-NewDiff actually do anything anymore?. But it doesn't seem that page is actively watched. Please comment. Thanks. Anomie ⚔ 18:33, 12 September 2012 (UTC)
Please make the edittools script into a default gadget so we can disable it and it is easier to import to other wikis and avoid code duplication. See MediaWiki talk:Edittools#Remove unused code for details. Helder 22:18, 1 August 2012 (UTC)
* EditTools[ResourceLoader|default|rights=edit]|EditToolsLoader.js
|| wgPageName == 'Special:Upload'
" from
MediaWiki:Common.js and the edit tools code from
MediaWiki:Common.js/edit.jsWhile I certainly agree in principle with turning this into a gadget, I see a few issues here:
These should be pretty easily resolvable, however. -— Isarra ༆ 17:49, 14 September 2012 (UTC)
#editpage-specialchars{ display: none; }
to
MediaWiki:Common.css (as
done on testwiki); anddisplay: block;
(see the
code on testwiki)Thanks to Yuvipanda, MBisanz, and Anomie, this has now been gadgetised as MediaWiki:Gadget-charinsert etc and is on by default for the time being. -— Isarra ༆ 07:22, 25 September 2012 (UTC)
I propose User:PrimeHunter/My subpages.js as a new gadget. PrimeHunter suggested this after I came to the help desk here following the Village pump discussion here. I already use it and it does exactly what I want, providing a link to all pages in my userspace at the top of every page I read. -- Toshio Yamaguchi ( tlk− ctb) 12:59, 14 September 2012 (UTC)
Comment. The closer at the Village Pump discussion said that "the consensus leans most towards opt-in gadget." I agree with that. There are already several gadgets in preferences for adding links to the sidebar or to menus at the top of every page. See: Special:Preferences#mw-prefsection-gadgets. This seems as useful, or more useful, than most of them.
A creative solution would be combine all the link-adding gadgets into one gadget in preferences that adds all the links into one menu in the sidebar. Maybe call that menu "More tools". By the way, Toshio Yamaguchi, you can ignore the more overzealous of the gadget deletionists. I do. Maybe Gadgets 2.0 that is being worked on will provide more tabs in preferences. Tables of content on preference tab pages would help too with sorting through the gadgets. -- Timeshifter ( talk) 01:13, 17 September 2012 (UTC)
I propose to create a tool for disambiguation detector as Spanish Wikipedia ( es:Wikipedia:Detector de desambiguaciones, German Wikipedia ( de:Wikipedia:Helferlein/Begriffsklärungs-Check), Galician Wikipedia ( gl:Wikipedia:Detector de homónimos) and Portuguese Wikipedia ( pt:Wikipédia:Detector de desambiguações) have. This tool is used to detect the links pointing disambiguations pages. For example, someone put the link Cuatro in an article in a television program, but would have to be this Cuatro (TV channel). And these links are marked yellow.
This gadget also marks the articles with topics of unclear notability.
I have already created the description page Wikipedia:Disambiguation detector. Now an administrator have that copy the code of Spanish Wikipedia es:MediaWiki:Gadget-DetectaDesambiguaciones.js, German Wikipedia de:MediaWiki:Gadget-bkl-check.js or Portuguese Wikipedia pt:MediaWiki:Gadget-desambiguacoes.js The administrator have to change the next code:
Categoría:Wikipedia:Desambiguación > Category:All disambiguation pages desambiguación > disambiguation Categoría:Wikipedia:Sin relevancia aparente > Category:Articles with topics of unclear notability SRA > (To the favorite word or phrase)
If anybody wants, can add more thinks to marks. Anybody checks the translation in Wikipedia:Disambiguation detector, because I know little English. -- Vivaelcelta { discusión · contributions} 18:12, 23 September 2012 (UTC)
importScript
, rather than jQuery ajax.apihighlimits
, since it uses callback
to get the results.clcategories
that is unlikely.As you are aware that I am doing lots of my efforts on Urdu Wiki. I often work on Wikipedia to update Interwiki links and Categories link between the two Wikipedias i.e. Urdu & English Wikipedia. I am using "Hot Interwiki" link in Urdu wiki ( find here) but couldn't succeed to find this link in English Wiki. Can you help me out to get this tool in English Wiki too so that I may enter Urdu interwiki link into English as I am usually make new categories on Urdu Wiki to categorize all article in a proper way. I only use English Wiki to enter Urdu interwiki and for this I've to spend lot of time to push the edit button on every single article on English Wiki to enter Urdu interwiki link.
I hope you will help me to get access to "Hot Interwiki" tool on English Wikipedia. Thanks -- ساجد امجد ساجد ( talk) 08:30, 20 October 2012 (UTC)
On high-res devices, especially those that have touch gestures such as tablets and smartphones, it would be nice to zoom in to find a finer image. I'm constantly finding myself going to the description page to view the image in a higher resolution.
I use recent versions of Mozilla Firefox on all of my Ubuntu and Android devices. I generally use 3G (soon to be 4G), but I have plenty of data allowance.
JamesHaigh ( talk) 01:42, 2 November 2012 (UTC)
srcset
attribute for high-resolution devices, including Javascript fallback for devices that don't yet support the property natively.
Anomie
⚔
03:27, 2 November 2012 (UTC)srcset
sounds great! How new is it? Does Firefox support it yet? Where is the correct place to report general feature requests on WP? I would still appreciate an option for progressive bitmap interlacing.
JamesHaigh (
talk)
04:13, 2 November 2012 (UTC)Please add an option to convert the TeX source into MathML for the browser to render. (Conversion should be done server-side, and cached.)
JamesHaigh ( talk) 04:14, 2 November 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I would like to propose adding the Direct imagelinks to Commons gadget. This was discussed briefly on the Village Pump a while back, where it received support from the few people who commented. It's already available on several other wikis. Kaldari ( talk) 18:44, 21 October 2012 (UTC)
A few months ago I proposed a simplified move proposal process, and shortly afterward there was consensus in favor of the idea. The specifics of the script weren't discussed very much, nor was the issue of testing it before enabling it by default. Testing and improving a script to the point where it's widely usable is difficult when there isn't an easy way to test it short of directly editing one's JS, so perhaps the best way to go about it is to add it as an opt-in gadget for a while first. So, I propose adding User:Yair rand/ControversialMoves.js as an opt-in gadget for users with the "move" right, so that it can be tested, discussed, and further improved until it is enabled by default. -- Yair rand ( talk) 02:29, 6 November 2012 (UTC)
Hi all, a recent RFC showed widespread consensus for adding syntax highlighting features to the edit box. I'd like to suggest adding meta:User:Remember the dot/Syntax highlighter.js as a gadget with the following note:
I tested the script in Internet Explorer 9 and 10 as well, and while it doesn't do anything, it doesn't appear to cause errors either. I was not able to test Safari, but it should work the same as Chrome. The bottom line is that while this script will not work for everyone, I think it is useful enough to consider making a gadget. — Remember the dot ( talk) 21:29, 10 November 2012 (UTC)
{{ edit protected}}
Over the two weeks that this request has been open no objections have been made and I have made a number of improvements to the script in that time also. I am sure that we will find additional ways to improve the script in the future, but right now I'd just like to have a stable version of it available through the preferences menu. Therefore, I'd like to ask that:
* [[:meta:User:Remember the dot/Syntax highlighter|Dot's syntax highlighter]], make syntax stand out colorfully in the edit box. Works best in [[Mozilla Firefox|Firefox]], works almost all of the time in [[Opera (web browser)|Opera]], and works most of the time in [[Google Chrome|Chrome]]. '''Should not''' be used with the browser's page zoom feature.
DotsSyntaxHighlighter[ResourceLoader]|DotsSyntaxHighlighter.js
— Remember the dot ( talk) 21:20, 24 November 2012 (UTC)
<br>
? Now thet we render HTML5, both <br>
and <br />
are valid.
[1] ---—
Gadget850 (Ed)
talk
14:43, 25 November 2012 (UTC)<br/>
is less confusing because it makes it obvious that the element has no closing tag. In fact, MediaWiki automatically converts <br>
to <br />
when rendering a page. The highlighter does not support other confusing syntaxes such as </br>
and <b><span>asymmetric tags</b></span>
either, both for performance reasons (the script is already quite slow on large pages) and to encourage a single clear, unambiguous syntax on Wikipedia. While supporting <br>
would probably not incur a significant performance penalty, I still feel that it's best to encourage only one syntax.It seems that few administrators are familiar enough with the gadgets pages to know how to add new ones, so I've put in the syntax highlighter gadget myself. Let me know if it causes any problems. — Remember the dot ( talk) 03:21, 6 December 2012 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
Archive 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 | Archive 7 |
We still get requests like this once in a while, so I think turning Sharebox into a WP:Gadget may be a good idea. Personally I strongly dislike Facebook, but that is just my POV. Arcandam ( talk) 01:47, 23 May 2012 (UTC)
This has already been suggested four years ago, I wonder why it hasn't been added as a gadget. I've been using this script now for several months, and it is simply amazing. Very, very helpful. -- bender235 ( talk) 18:49, 7 June 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The AFC Helper Script ( code) is heavily used in reviewing by WikiProject Articles for creation. It is tested and works in all major browsers (Chrome, Firefox, IE, Opera, Safari) and skins (Monobook, Vector, Modern), and can be used by members of all user groups (except for creating submissions, which is only possible by autoconfirmed, nor on protected or title-blacklisted pages (obviously)). In its three-year history, it has grown to something beyond a simple script by Tim; it is now actively maintained by multiple users, including Mabdul, Excirial, and I. I believe that making this script a gadget would invite more users to participate in a project that is currently suffering from a massive backlog (see various talk page threads: Time to invite new users!, Backlog too large, Backlog is only going to get worse.), since prospective reviewers do not need to learn the complicated parameters for {{ AFC submission}} nor do they need to muddle in their userspace Javascript. It will also make the project known to those who are unaware of its existence. Thanks. — The Earwig (talk) 23:33, 23 June 2012 (UTC)
I think we are done here, right? Who can we ask to implement it? Arcandam ( talk) 14:04, 1 July 2012 (UTC)
Remember that watchlist RfC? It established that highlighting of unwatched changes should be off by default, but that an option should be available to enable it in preferences. Therefore, I would like to ask that two gadgets be enabled using the CSS at WP:CUSTOMWATCH: one enabling bold styling for unwatched changes, and one enabling an underscore (these received the most support in the RfC). Also, could you put a link to WP:CUSTOMWATCH—in case they want to make changes that aren't one of the gadgets—in the description of the gadgets? Thanks, David 1217 What I've done 15:01, 6 July 2012 (UTC)
See https://bugzilla.wikimedia.org - It has a link for advanced search ( Special:Search) in the sidebar. Is there any reason this link can not be added to the Wikipedia sidebar? This would allow people to do searches in a new browser tab without covering the current page.
Can a gadget allow one to place this link in the sidebar? -- Timeshifter ( talk) 10:56, 7 July 2012 (UTC)
All users have a gadget enabled by default for asking questions at Wikipedia:Teahouse, hence the smooth question box that pops up there. After some talk of adding another gadget for responding to existing questions, I'd written a script for that purpose, which I understand several editors have been using for a while, including some Foundation people. I wonder if someone could have a look into the possibility of enabling this too as a default gadget.
The aim of this script is to make it easier for new users to respond to these discussions, when they don't necessarily understand that this entails editing the section. Once in a while, people actually ask how to post a response. The script is based on the Ask gadget, and uses a similar input box, for uniformity. Equazcion (talk) 14:56, 10 Aug 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I would like to propose adding a new gadget, which would be enabled by default. This is based on Andrew's #Teahouse gadget discussed above, but more flexible and with some slight changes in behaviour. Basically wherever the template {{ commentr}} is used, it creates a link which pops up a small form. This can be used to leave a message, which is saved as a new section either on the current page or on a page specified as a template parameter. If JavaScript is not available, or the browser's implementation is FUBAR (glares at Internet Explorer 6), then the link will just go to the standard edit form.
The initial use case for this will be part of my Help Project fellowship. The idea is to place this template on certain important help pages, and collect feedback in a centralised location such as Wikipedia:Help Project/Feedback for attention and action by Help Project members. Since many of the people using the Help pages are not experienced Wikipedians, having a simple popup form without the complexities of the standard editing form will be better for them. In creating this gadget I've attempted to make it fairly flexible, so that it can be adopted for other projects in future if desired. The text and style of the form are all customisable by using template parameters.
I've tested in most major browsers (Chrome, Firefox, IE 7+, Safari), and apart from the above mentioned IE6 problem didn't see any issues. If people want to see the code it's currently at User:The wub/commentr.js and User:The wub/commentr.css, and if you wish to test you can add the following to Special:MyPage/common.js:
importScript( 'User:The wub/commentr.js' );
importStylesheet( 'User:The wub/commentr.css' );
If there are no problems or objections, I'd like to go ahead and enable this next week. the wub "?!" 12:54, 17 June 2012 (UTC)
once they ... click Save they get dumped to a different page from the one they were looking at- how so? -- Redrose64 ( talk) 20:58, 19 June 2012 (UTC)
The standard editing form has a lot of features that are important for normal editing of the encyclopediaI was under the impression that you were discussing the regular Edit tab, or a section's [edit] link. Upon hitting "Save page", those take you back where you came from. -- Redrose64 ( talk) 12:05, 20 June 2012 (UTC)
I would oppose adding such a gadget based upon the idea that it would be enabled by default. -- Nouniquenames ( talk) 04:48, 24 June 2012 (UTC)
As suggested by Arcandam, I have added this to the gadgets list for people to test, although it is not yet enabled by default. the wub "?!" 21:18, 24 June 2012 (UTC)
Comment as the instigator and creator (with significant help) of the current {{ Leave feedback}} system, I have some comments.
Since this page is for proposing addition of gadgets, I posted a pair of removal proposals at Wikipedia talk:Gadget#Deprecate textareasansserif? and Wikipedia talk:Gadget#Does Gadget-NewDiff actually do anything anymore?. But it doesn't seem that page is actively watched. Please comment. Thanks. Anomie ⚔ 18:33, 12 September 2012 (UTC)
Please make the edittools script into a default gadget so we can disable it and it is easier to import to other wikis and avoid code duplication. See MediaWiki talk:Edittools#Remove unused code for details. Helder 22:18, 1 August 2012 (UTC)
* EditTools[ResourceLoader|default|rights=edit]|EditToolsLoader.js
|| wgPageName == 'Special:Upload'
" from
MediaWiki:Common.js and the edit tools code from
MediaWiki:Common.js/edit.jsWhile I certainly agree in principle with turning this into a gadget, I see a few issues here:
These should be pretty easily resolvable, however. -— Isarra ༆ 17:49, 14 September 2012 (UTC)
#editpage-specialchars{ display: none; }
to
MediaWiki:Common.css (as
done on testwiki); anddisplay: block;
(see the
code on testwiki)Thanks to Yuvipanda, MBisanz, and Anomie, this has now been gadgetised as MediaWiki:Gadget-charinsert etc and is on by default for the time being. -— Isarra ༆ 07:22, 25 September 2012 (UTC)
I propose User:PrimeHunter/My subpages.js as a new gadget. PrimeHunter suggested this after I came to the help desk here following the Village pump discussion here. I already use it and it does exactly what I want, providing a link to all pages in my userspace at the top of every page I read. -- Toshio Yamaguchi ( tlk− ctb) 12:59, 14 September 2012 (UTC)
Comment. The closer at the Village Pump discussion said that "the consensus leans most towards opt-in gadget." I agree with that. There are already several gadgets in preferences for adding links to the sidebar or to menus at the top of every page. See: Special:Preferences#mw-prefsection-gadgets. This seems as useful, or more useful, than most of them.
A creative solution would be combine all the link-adding gadgets into one gadget in preferences that adds all the links into one menu in the sidebar. Maybe call that menu "More tools". By the way, Toshio Yamaguchi, you can ignore the more overzealous of the gadget deletionists. I do. Maybe Gadgets 2.0 that is being worked on will provide more tabs in preferences. Tables of content on preference tab pages would help too with sorting through the gadgets. -- Timeshifter ( talk) 01:13, 17 September 2012 (UTC)
I propose to create a tool for disambiguation detector as Spanish Wikipedia ( es:Wikipedia:Detector de desambiguaciones, German Wikipedia ( de:Wikipedia:Helferlein/Begriffsklärungs-Check), Galician Wikipedia ( gl:Wikipedia:Detector de homónimos) and Portuguese Wikipedia ( pt:Wikipédia:Detector de desambiguações) have. This tool is used to detect the links pointing disambiguations pages. For example, someone put the link Cuatro in an article in a television program, but would have to be this Cuatro (TV channel). And these links are marked yellow.
This gadget also marks the articles with topics of unclear notability.
I have already created the description page Wikipedia:Disambiguation detector. Now an administrator have that copy the code of Spanish Wikipedia es:MediaWiki:Gadget-DetectaDesambiguaciones.js, German Wikipedia de:MediaWiki:Gadget-bkl-check.js or Portuguese Wikipedia pt:MediaWiki:Gadget-desambiguacoes.js The administrator have to change the next code:
Categoría:Wikipedia:Desambiguación > Category:All disambiguation pages desambiguación > disambiguation Categoría:Wikipedia:Sin relevancia aparente > Category:Articles with topics of unclear notability SRA > (To the favorite word or phrase)
If anybody wants, can add more thinks to marks. Anybody checks the translation in Wikipedia:Disambiguation detector, because I know little English. -- Vivaelcelta { discusión · contributions} 18:12, 23 September 2012 (UTC)
importScript
, rather than jQuery ajax.apihighlimits
, since it uses callback
to get the results.clcategories
that is unlikely.As you are aware that I am doing lots of my efforts on Urdu Wiki. I often work on Wikipedia to update Interwiki links and Categories link between the two Wikipedias i.e. Urdu & English Wikipedia. I am using "Hot Interwiki" link in Urdu wiki ( find here) but couldn't succeed to find this link in English Wiki. Can you help me out to get this tool in English Wiki too so that I may enter Urdu interwiki link into English as I am usually make new categories on Urdu Wiki to categorize all article in a proper way. I only use English Wiki to enter Urdu interwiki and for this I've to spend lot of time to push the edit button on every single article on English Wiki to enter Urdu interwiki link.
I hope you will help me to get access to "Hot Interwiki" tool on English Wikipedia. Thanks -- ساجد امجد ساجد ( talk) 08:30, 20 October 2012 (UTC)
On high-res devices, especially those that have touch gestures such as tablets and smartphones, it would be nice to zoom in to find a finer image. I'm constantly finding myself going to the description page to view the image in a higher resolution.
I use recent versions of Mozilla Firefox on all of my Ubuntu and Android devices. I generally use 3G (soon to be 4G), but I have plenty of data allowance.
JamesHaigh ( talk) 01:42, 2 November 2012 (UTC)
srcset
attribute for high-resolution devices, including Javascript fallback for devices that don't yet support the property natively.
Anomie
⚔
03:27, 2 November 2012 (UTC)srcset
sounds great! How new is it? Does Firefox support it yet? Where is the correct place to report general feature requests on WP? I would still appreciate an option for progressive bitmap interlacing.
JamesHaigh (
talk)
04:13, 2 November 2012 (UTC)Please add an option to convert the TeX source into MathML for the browser to render. (Conversion should be done server-side, and cached.)
JamesHaigh ( talk) 04:14, 2 November 2012 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I would like to propose adding the Direct imagelinks to Commons gadget. This was discussed briefly on the Village Pump a while back, where it received support from the few people who commented. It's already available on several other wikis. Kaldari ( talk) 18:44, 21 October 2012 (UTC)
A few months ago I proposed a simplified move proposal process, and shortly afterward there was consensus in favor of the idea. The specifics of the script weren't discussed very much, nor was the issue of testing it before enabling it by default. Testing and improving a script to the point where it's widely usable is difficult when there isn't an easy way to test it short of directly editing one's JS, so perhaps the best way to go about it is to add it as an opt-in gadget for a while first. So, I propose adding User:Yair rand/ControversialMoves.js as an opt-in gadget for users with the "move" right, so that it can be tested, discussed, and further improved until it is enabled by default. -- Yair rand ( talk) 02:29, 6 November 2012 (UTC)
Hi all, a recent RFC showed widespread consensus for adding syntax highlighting features to the edit box. I'd like to suggest adding meta:User:Remember the dot/Syntax highlighter.js as a gadget with the following note:
I tested the script in Internet Explorer 9 and 10 as well, and while it doesn't do anything, it doesn't appear to cause errors either. I was not able to test Safari, but it should work the same as Chrome. The bottom line is that while this script will not work for everyone, I think it is useful enough to consider making a gadget. — Remember the dot ( talk) 21:29, 10 November 2012 (UTC)
{{ edit protected}}
Over the two weeks that this request has been open no objections have been made and I have made a number of improvements to the script in that time also. I am sure that we will find additional ways to improve the script in the future, but right now I'd just like to have a stable version of it available through the preferences menu. Therefore, I'd like to ask that:
* [[:meta:User:Remember the dot/Syntax highlighter|Dot's syntax highlighter]], make syntax stand out colorfully in the edit box. Works best in [[Mozilla Firefox|Firefox]], works almost all of the time in [[Opera (web browser)|Opera]], and works most of the time in [[Google Chrome|Chrome]]. '''Should not''' be used with the browser's page zoom feature.
DotsSyntaxHighlighter[ResourceLoader]|DotsSyntaxHighlighter.js
— Remember the dot ( talk) 21:20, 24 November 2012 (UTC)
<br>
? Now thet we render HTML5, both <br>
and <br />
are valid.
[1] ---—
Gadget850 (Ed)
talk
14:43, 25 November 2012 (UTC)<br/>
is less confusing because it makes it obvious that the element has no closing tag. In fact, MediaWiki automatically converts <br>
to <br />
when rendering a page. The highlighter does not support other confusing syntaxes such as </br>
and <b><span>asymmetric tags</b></span>
either, both for performance reasons (the script is already quite slow on large pages) and to encourage a single clear, unambiguous syntax on Wikipedia. While supporting <br>
would probably not incur a significant performance penalty, I still feel that it's best to encourage only one syntax.It seems that few administrators are familiar enough with the gadgets pages to know how to add new ones, so I've put in the syntax highlighter gadget myself. Let me know if it causes any problems. — Remember the dot ( talk) 03:21, 6 December 2012 (UTC)