User talk:Remember the dot/Archive/2016

Syntax highlighter: Fixed height

Is it really necessary to force a fixed height?

I am not abe to resize the textarea anymore in the down right corner (Chrome).

Can't it re-calculate the size on change? --Unsigned, 2016-04-27

Sorry about that. It used to work, and I just fixed it so that it works again now. —Remember the dot ^(talk) 18:21, 29 April 2016 (UTC)

Bug report

Type: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36 Vector skin Most Browsing, Watchlist and Editing gadgets (not wikEd or Yet Another AFC Helper Script); MoreMenu, Tracked Bugs

I get a visual bug: while editing a section, text does not display in the editing box sometimes; it's solid white with highlight markers faintly visible. The only workaround is to hit "edit the entire page" and then edit the section. Changing the contents of the subsection fixes this issue; once I've changed something in a problem section, it becomes editable alone. This has been going on for quite a while but I honestly couldn't be arsed to report it. It's pretty aggravating, though. Ogress 01:36, 27 May 2016 (UTC)

That stinks. Can you try different browsers or different pages to narrow down when the problem occurs? —Remember the dot ^(talk) 03:56, 27 May 2016 (UTC)

Just happened at Andean civilizations: section was fine when I edited;

• after I made changes to the page and hit "preview", it went blank (but I could save it and it was fine; the issues are strictly visual problems of the interface). Here's what I see

I can reopen the intro section right now and it is like that; if I wanted to edit that first section now, I'd have to hit "edit the whole page" to do so. Whatever triggers that bug is triggering it right now. Ogress 06:50, 27 May 2016 (UTC)

• This edit turned the page into goo
• this edit fixed it. Ogress 18:52, 28 May 2016 (UTC)
• A wild goo appears! This was goo before and after I edited it (using the "edit full page" workaround) Ogress 19:25, 28 May 2016 (UTC)
• Goo before I edited the "further links" section, but fixed after. Ogress 19:52, 28 May 2016 (UTC)
• Goo appears in the section after this edit. Ogress 23:30, 28 May 2016 (UTC)
• Goo appeared in the intro after this edit. It happened a few times more before this but I didn't care to document it. Ogress 02:26, 29 May 2016 (UTC)
• Started editing again, this is goo before and after my edits. Ogress 05:20, 29 May 2016 (UTC)

I wasn't trying to imply that the problem will disappear and reappear depending on the time of day. I need you to try disabling your extra gadgets, editing with a different web browser, editing on a different computer, etc. to narrow down the circumstances that can trigger it. —Remember the dot ^(talk) 22:58, 30 May 2016 (UTC)

Syntax highlighter

Hey! If you are around, could you please take a look at the discussion regarding the Syntax highlighter gadget at Wikipedia:Village pump (technical)#Highlighting of text and text are separated? - NQ (talk) 11:03, 14 September 2016 (UTC)

Appreciate the quick fix. Thank you very much. - NQ (talk) 07:00, 15 September 2016 (UTC)

Syntax highlighter broken?

Whatever was done to the syntax highlighter today, it is now broken. It no longer works in SeaMonkey or Firefox. When I open any existing article for editing, the browser essential slows to a crawl and gets "greyed-out" on my screen and I get a succession of "unresponsive script" warnings, as if it were stuck in an infinite loop. It worked fine a day or two ago. — Quicksilver (Hydrargyrum)^{T @} 18:25, 15 September 2016 (UTC)

FYI, it still works (better) for me in Firefox 48.0.1 for Mac OS. – Jonesey95 (talk) 18:52, 15 September 2016 (UTC)

User:Hydrargyrum/monobook.js contains a call to "addOnloadHook", which may cause problems. See this discussion, which I do not fully understand. Pinging Hydrargyrum. – Jonesey95 (talk) 18:57, 15 September 2016 (UTC)

Ping Jonesey95 Thanks for the link. Until I figure out what's happening, I'll just leave syntax highlighting disabled in my "Gadget" preferences. Strangely enough, even as I'm typing this with syntax highlighter disabled, I'm seeing syntax highlighting in the edit window, but no unresponsive script timeouts, i.e., it's working like it did when I first activated syntax highlighting a couple of years ago. — Quicksilver (Hydrargyrum)^{T @} 19:21, 15 September 2016 (UTC)

Hey! In your common.js you are already importing the script using the line mw.loader.load('//www.mediawiki.org/w/index.php?title=MediaWiki:Gadget-DotsSyntaxHighlighter.js&action=raw&ctype=text/javascript'); so you don't need to have the gadget enabled in your preferences and that's why it still works. Maybe that was part of the problem? - NQ (talk) 19:43, 15 September 2016 (UTC)

NQ — That must be it. I disabled the line in my common.js that loads the syntax highlighter script, leaving the CSS color overrides, and re-enabled the syntax highlighter in my Gadget preferences. It seems to behave normally again. I find it strange, though, that the setup worked fine for months and suddenly broke today. I'm induced to conclude that it didn't have anything to do with the syntax highlighter script, but rather some change that was made in the past day or two at wikipedia.org or wikimedia.org. Thanks for the pointers. — Quicksilver (Hydrargyrum)^{T @} 20:10, 15 September 2016 (UTC)

You shouldn't load the syntax highlighter twice. Before yesterday's changes (see Wikipedia:Village pump (technical)#Highlighting of text and text are separated), loading it twice caused severe performance problems. After yesterday's changes, loading it twice will break your browser altogether. If a lot of people are making this mistake, we should add a note to the documentation. —Remember the dot ^(talk) 01:10, 16 September 2016 (UTC)

By the way, if in the future you save some user JavaScript that locks you out of editing pages, you can still edit and fix the JavaScript page if you temporarily disable JavaScript in your web browser. —Remember the dot ^(talk) 01:15, 16 September 2016 (UTC)

I had the same problem but a note on the documentation page would not have helped because I had no idea what was causing the problem or where to look for a solution. A couple of editors at the help desk figured it out for me. Leschnei (talk) 13:33, 19 September 2016 (UTC)

very few instances of it on en.wiki (search results) - NQ (talk) 13:51, 19 September 2016 (UTC)