Closed
Bug 1242940
Opened 8 years ago
Closed 8 years ago
Replace {{Xref_csspercentage}} occurrences with {{cssxref("<percentage>")}}
Categories
(Developer Documentation Graveyard :: Macros/Templates, defect)
Developer Documentation Graveyard
Macros/Templates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: teoli, Assigned: snakenas, Mentored)
References
Details
(Whiteboard: [good first bug])
We have 182 occurrences of {{xref_csspercentage}}, a macro we want to delete [1]. This task is about to go on each of these MDN pages, to edit the page and to replace the occurrence of {{xref_csspercentage}} with {{cssxref("<percentage>")}}, to save it and to check that the link is working. You need an MDN account and the ability to use a WYSIWYG editor to perform this task. [1] https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=xref_csspercentage
Comment 1•8 years ago
|
||
Hello. I would be happy to work on this bug but I dont have an MDN account and when I tried to create an account, the website says that the account creation is unabled right now. Could you help me with that? Thank you.
Reporter | ||
Comment 2•8 years ago
|
||
I can. Ping me (e-mail or here or IRC) when you are online and I can open account creation for a few minutes.
Updated•8 years ago
|
Mentor: sebastianzartner
Hello I would like to work on this bug, I have created an account at MDN. Could I also have more information on this and how this works?
Comment 4•8 years ago
|
||
Hi snakenas, as teoli says in comment 0 the steps to fix this bug are to replace all occurrences of {{xref_csspercentage}} by {{cssxref("<percentage>")}} on the pages listed at https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=xref_csspercentage. Currently there are 100 pages left that need to be fixed. Sebastian
Updated•8 years ago
|
Assignee: nobody → snakenas
Hi, Just as a notification, the pages should be fixed now.
Comment 6•8 years ago
|
||
Yes, thank you snakenas! Sebastian
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•