503861 - [qmo2] Rendering artifacts (gray background) when trying to edit a document

Status: RESOLVED INVALID

(quality.mozilla.org :: Website, defect, P3)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

Attachment: Screenshot

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1pre) Gecko/20090709 Shiretoko/3.5.1pre ID:20090709035801

I don't think that it is caused by any ugliness of the richtext editor on authstage but when you click the edit tab to edit the document referenced above parts of the screen are grayed. When you scroll up/down those parts are invalidated and corrected. More a core/layout issue? See the screenshot.

Comment 1

[Aakash Desai [:aakashd]]

WFM on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 ID:20090624012136


and safari 4.0

Tomcat, do you see this on the url provided by henrik?

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

It doesn't happen regularly. Just click through some of the documents and try to edit the pages.

Comment 3

[Paul Craciunoiu [:paulc]]

How often does this happen?

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

Less often. Probably for pages which are not in the cache? I cannot tell right now. Just try to edit pages on authstage. I hope you will see it.

Comment 5

[Paul Craciunoiu [:paulc]]

We don't really have cache... but it may have to do with the browser cache and we could potentially set the tinymce scripts to expire more often than the rest. That would take some work, though.
Try keeping track of how often it happens and post here when you're annoyed mentioning it. Maybe that can hint as to why it happens. Btw, what OS? Mac?

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

I meant the browser cache. Sorry for the confusion. Yes, it happens on OS X as what the platform says. I haven't tried to reproduce it on another platform yet.

Comment 7

[Aakash Desai [:aakashd]]

This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.

Comment 8

[Aakash Desai [:aakashd]]

This bug is being moved to a resolved state of invalid due to one of the following reasons:

- we're moving to wordpress and so all drupal cruft is not going to be fixed
- the feature is not supported on the new qmo, at least for this release.