Closed Bug 935897 Opened 11 years ago Closed 11 years ago

Editor stylesheet does not match the document stylesheet

Categories

(developer.mozilla.org Graveyard :: Editing, defect, P1)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Jeremie, Unassigned)

References

Details

Attachments

(1 file)

When you edit a document, the styles applied within the editor are different than the one use to display the document. This especially obvious on titles and tables.
This happens also for syntax boxes. Ali: I propose to block on this. It is not a big amount of work, and this nullify the usage of a wysiwig editors. It will raise the bar for new editors that will have to understand why it is different.
Flags: needinfo?(aspivak)
Not that I don't believe you but can I get a screenshot or can you let me know what element(s). A link would be hot too.
H2 h3 are old style so also are the in-content spec boxes.
Blocks: MDNLaunchBlockers
No longer blocks: 910513
Component: Design / user experience → Editing
JYP: Can you confirm that the cache clearing fixed all of the issues listed in this ticket? They should all be solved. Cache should no longer be an issue moving forward because the URLs are all cache-busted now.
Flags: needinfo?(aspivak) → needinfo?(jypenator)
I confirm that the cache clearing fixed all the issues in the editor stylesheet described this. I only see some wrong <h2> styling in the translation stylesheet (edit window). David, is this the same (and there I must investigate by clearing the cache again), or is it a different stylesheet and therefore a new bug. If a different stylesheet, one can close this bug.
Flags: needinfo?(dwalsh)
Flags: needinfo?(jypenator)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dwalsh)
Resolution: --- → FIXED
I'm reopening this one. I again get a lot of the old styles in the editor pages. As it was fixed last week by a cache clearing, this means that something is corrupting my cache again! Is it possible that if I access the site not logged in or not in beta mode that could "corrupt" the locale cache?
Status: RESOLVED → REOPENED
Flags: needinfo?(dwalsh)
Resolution: FIXED → ---
I'm wondering if it's a between-two-designs caching issue. I'm going to leave this open for now. So confused because this doesn't happen locally.
Flags: needinfo?(dwalsh)
I will double check in a couple of days if is still happens. (Auto-feedbacking me so that I don't forget)
Flags: needinfo?(jypenator)
:teoli - how does this look now?
No change. When I clear the cache it is ok for some time, then goes back to the old style.
Flags: needinfo?(jypenator)
:teoli, are you still seeing the strange caching behaviour?
Flags: needinfo?(jypenator)
Severity: normal → minor
Priority: -- → P1
Yes, I see no difference. Māris, do you see the correct styles in production (in an edit window)?
Flags: needinfo?(jypenator)
I found a class on the body that we may not need. PR here and CSS collisions should finally stop: https://github.com/mozilla/kuma/pull/2016
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/c96696f3db885e4ecd3c25590a5e508bb8ccb886 fix bug 935897 - Remove unneeded class from ckeditor content body https://github.com/mozilla/kuma/commit/48b7eebf2297600a28d17e31c6f1777f2dea1ca0 Merge pull request #2016 from darkwing/stylesheet-935897 fix bug 935897 - Remove unneeded class from ckeditor content body
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
It looks ok today \o/ I will keep an eye opened, but I'm fairly confident it is fixed.
Status: RESOLVED → VERIFIED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: