Page MenuHomePhabricator

CX2 - Validation for page title
Closed, DeclinedPublic


This task is a follow-up of T190804: CX2: Error for invalid characters in the title.

(1) Are we going to catch the titles with characters that are silently dropped?
e.g. :Mavetuna will be published as Mavetuna (the colon is dropped, according to the following restriction:

A pagename cannot begin with a colon :.

Screen Shot 2018-06-11 at 6.14.32 PM.png (225×968 px, 36 KB)

(2) Although # is a invalid character, it's allowed in translated page titles in cx-testing. Even more, having # in the page title will make other invalid chars "valid", so a page title like # < > [ ] | { } _ seems to be valid in cx2-testing.

(3) "H#e|ge|||||||||||||||||" (no quotes) also seems to be valid and redirects to (discarding all characters after H):

Screen Shot 2018-06-11 at 4.47.10 PM.png (376×931 px, 53 KB)

(4) Not all errors are communicated clearly to a user - in the screenshot the error message appears, but there are no details in the side panel. In the screenshot, the focus is on the invalid title, but no side panel error is displayed.

Screen Shot 2018-06-25 at 2.36.55 PM.png (262×1 px, 55 KB)

(5) The documentation pages needs to be updated - and have slightly different list of restricted characters that are not allowed in the page title.

Event Timeline

Pginer-WMF moved this task from Needs Triage to CX2 on the ContentTranslation board.
Vvjjkkii renamed this task from CX2 - Validation for page title to 8aaaaaaaaa.Jul 1 2018, 1:02 AM
Vvjjkkii raised the priority of this task from Low to High.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
Pginer-WMF added a subscriber: Pginer-WMF.

Those are valid and interesting edge cases for invalid titles. However, given that when translating users are starting from a title that was already valid, these seem less likely to occur in practice. If reality proves otherwise, we can consider reopening this ticket.