Consider the following wikicode:
{| style="background-color: #eb6841; style="text-align: center;"
It seems that with Tidy previously, the table would not be colored red, but with RemexHTML now it does. Should this be flagged by the linter?
Notice about a parsing change that causes this will go out in Tech News when more information will be given.
Consider the following wikicode:
{| style="background-color: #eb6841; style="text-align: center;"
It seems that with Tidy previously, the table would not be colored red, but with RemexHTML now it does. Should this be flagged by the linter?
This is more likely to do with, https://github.com/wikimedia/mediawiki/commit/59bb8864a23f3df120789c7619ef07acefa27b9c
Ah OK. But since this parsing change, a page's layout can break via an unrelated edit, so I would have expected a notice in Tech News to at least prevent confusion.
Sorry about that, it's my fault. There was a bit of discussion about the repercussions of the change at the bottom of, https://gerrit.wikimedia.org/r/c/mediawiki/core/+/471363
Do you think it's worth adding to the next edition of Tech News?
A broken page layout is not always noticed, and even then not always reported. So I think it would be good to let technical editors know which patterns are now treated differently.
Ok, I added in here, https://meta.wikimedia.org/w/index.php?title=Tech/News/2019/02&type=revision&diff=18722210&oldid=18709064&diffmode=source
Hey, I'm handling Tech News for this week.
How would you summarize that change in one sentence? How will in impact users? Do you have a tracking ticket on Phabricator about that?
Thanks!
Since I have no reply but I have to wrap-up and freeze the current issue, I've posted your previous explanation to next week issue.
Please provide there a shorter explanation. :)
Not from me. I assumed you were asking @Arlolra. I don't understand the change well enough to be able to figure out which wikicode patterns are now treated differently.
How about ...
Quoted attributes used to require being followed by a space, now they do not. Since this is a change to how a page is parsed it could cause unmodified portions of the page to render differently on edit.
Thanks! I simplified that a fair bit, for the benefit of non-native and/or non-technical readers. You can see the draft at m:Tech/News/2019/03.