Closed
Bug 768343
Opened 13 years ago
Closed 13 years ago
<dfn> elements not being migrated properly
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: teoli, Unassigned)
References
()
Details
(Whiteboard: u=contributor c=wiki s= p=)
<dfn> is often used and is safe. It should be whitelisted.
Numerous pages use it (all CSS references are broken because of this)
Comment 1•13 years ago
|
||
Same deal here: can fork & edit https://github.com/mozilla/kuma/blob/master/apps/wiki/models.py#L38 and send a PR to add more tags.
Updated•13 years ago
|
Reporter | ||
Comment 2•13 years ago
|
||
Unfortunately the models.py#L38 already have the <dfn> (and <sub>, <sup>, <caption>) element but the problem is still there.
Reporter | ||
Comment 3•13 years ago
|
||
Oh I have understood!
The tags on the pages has been converted to <dfn> and we have to manually edit the pages that have them!
Is there a way to automate that (>100 pages!)
Reporter | ||
Comment 4•13 years ago
|
||
It may be that import script from DekiWiki is doing this. Old revisions are ok (<dfn> imported correctly), but recent revisions are not.
See https://developer-new.mozilla.org/en-US/docs/CSS/transition-duration$history
the May 7th revision has been imported correctly. But June 1st not. So the more editions happen on the DekiWiki site, the more such problems are imported into the Kuma site.
Updated•13 years ago
|
Assignee: jkarahalis → nobody
Summary: <dfn> must be whitelisted → <dfn> elements not being migrated properly
Comment 5•13 years ago
|
||
Here's what I think the problem is: When a document is saved on Kuma (or when it's initially migrated), a copy of the content is run through the Bleach sanitizer and saved in the DB. That copy is what gets served up when you view the page.
If the Bleach whitelist is changed, there's no mechanism to re-save any documents with tags that were previously disallowed by Bleach. So, try editing and saving the affected documents and see if that fixes things.
If that fixes things, maybe we can look at adding a tool to re-save documents after changes in the whitelist. Pending that, just edit & resave documents with tags that have been newly added to the whitelists.
Comment 6•13 years ago
|
||
...and having said the above, re-saving doesn't seem to fix it, despite <dfn> being in the white list. Still looking at things.
Comment 7•13 years ago
|
||
Oh, wait, no I think it did work:
https://developer-new.mozilla.org/en-US/docs/CSS/transition-duration
I might have just run afoul of bug 765649 and needed to hit refresh. Let me see if I can repeat on CSS/animation
Updated•13 years ago
|
Whiteboard: u=contributor c=wiki s=2012-07-18 p=
Comment 8•13 years ago
|
||
I think this one is actually fixed
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Whiteboard: u=contributor c=wiki s=2012-07-18 p= → u=contributor c=wiki s= p=
FWIW, I still see a lot of <dfn> on the page here:
https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Object/getOwnPropertyDescriptor
Reporter | ||
Comment 10•13 years ago
|
||
Are you sure? I don't see any...
Comment 11•13 years ago
|
||
Ha, don't see them any more. Either someone ad-hoc fixed it, flushed it etc. or some other issue happened (web cache somewhere? not the browser cache issue on my side for sure). I should post a screenshot the next time to be more credible :)
Reporter | ||
Comment 12•13 years ago
|
||
:-) Don't worry. On this one I believe it may have been cache issue. I still get a few of them once in a while and usually an edit followed by a save fix them.
Don't bother about the screenshot, just report the future links :-)
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•