| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This was used to test an experimental parsoid feature before deployment,
but the testing was successful.
Bug: T382464
Follows-Up: I194a9550500bf7ece215791c51d6feb78a80b1a8
Change-Id: Ib91a17868352722dc3570b07856423733f1b2368
|
| |
|
|
|
|
| |
This now aligns with Parsoid commit b9166ba69b1148e5b8d62dd200fa25fc79116b96
Change-Id: I5ca957b030639815786138b76c65720d706c13a6
|
| |
|
|
|
|
| |
This now aligns with Parsoid commit 3c3e96d168b5b5a5fe90520ea23f938a7a59181d
Change-Id: Iadbe23dcc4b9ee68ad10220623ad9edae0b41b40
|
| |
|
|
|
|
|
| |
Per https://meta.wikimedia.org/wiki/Talk:Interwiki_map/Archives/2024#RFC
Bug: T71997
Change-Id: I2b6b63f7809e5801c78de370c828bbca5fe95e64
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Arabic translation of red-link-title was modified again in change
Id00b720194 (commit 30c622c091), requiring another fix mirroring change
I8f2930802a (commit 6cbd9e5263).
Test with:
composer phpunit -- --testsuite parsertests --filter=T236183
Bug: T369694
Change-Id: I19090fe523e0a5c17bc1c30ee31edce24f541e6b
Follows-Up: Id00b720194d3a715050cbce55e40ca11b34212ce
|
| |
|
|
|
|
|
|
|
| |
The Arabic translation of red-link-title was modified in change
I47769df5dc (commit dfd748033e).
Bug: T368383
Change-Id: I8f2930802a6b161ba44205d6b6d114d223be3cde
Follows-Up: I47769df5dc91ad12d817e117fe931b1452e8b2ef
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Legacy parser can now output headings using a more accessible markup,
which is also identical to the markup used by the Parsoid parser.
Changes to client-side JS and CSS necessary to support the new markup
have already been merged in earlier commits.
includes/skins/Skin.php
includes/ServiceWiring.php
* Define a new skin option, 'supportsMwHeading', which can be used
to toggle the new markup per-skin.
* Update the built-in fallback skin to enable it. This affects the
output in parser tests.
docs/config-schema.yaml
includes/config-schema.php
includes/config-vars.php
includes/MainConfigNames.php
includes/MainConfigSchema.php
* Add a new configuration setting, 'ParserEnableLegacyHeadingDOM',
which can be used to toggle the new markup per-site.
includes/OutputTransform/Stages/HandleSectionLinks.php
* Output new heading HTML for skins that enabled the option.
tests/*
* Duplicate parser tests that cover heading generation to cover both
new and old markup. Update other parser tests to use new markup.
* Add some unit and integration tests for the behavior of the skin
option and some parser tests for edge cases of the new markup.
Bug: T13555
Change-Id: I1180169a8e83af834c2984ba16089e6277f2a8dd
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This now aligns with Parsoid commit 51baccc8741108a9e3f763f2c19c6ce6eda55ac4
Three tests needed to be disabled because they had dependencies on features
not included in core's CI:
* {{#if}} used in tests added by I71c38b42ac9bfb7137f2e34df70bdfa139abced7
but only provided by the ParserFunctions extension
* <poem> used in tests added by I5a6356a82251881a5f841b36a7f26879fc611138
but only provided by the Poem extension
In addition, the "multiline" part of the "Expansion of multi-line..."
parser tests seems to have been lost at some point. My best guess is
that the definition of `Template:1x` initially included an extra
newline which was lost, maybe during an unrelated stripping of
leading/trailing whitespace in `!! article` clauses. In any case,
these tests are no longer testing the thing they say they are.
These will be fixed in a follow up.
Change-Id: Ia9144634625f176fbea11f3d2ef4b21a5492e99b
|
|
|
This now aligns with Parsoid commit f4a186b9b63f9216b2d7a363aa1ed45aef59b0c4
Change-Id: Ie48f0c03a1539a575389f766b994c54a75bfb3e1
|
