Closed Bug 73065 Opened 24 years ago Closed 23 years ago

The table background color will keep the default color in Composer when change the background first.

Categories

(Core Graveyard :: GFX, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: amyy, Assigned: kmcclusk)

Details

Steps to reproduce: 1. Launch the 03-16/19 Mtrunk build. 2. Open Composer, and change the background color other than default. 3. Insert a table. Result: The table background color will keep the default color which is different than the rest parts in Composer, and when you brower it, the background color will be only one that matched the changing at begining.
table cells have their own color properties, the table itself is not transparent. Marking as invalid
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
But if you browser the page, the background of the table(cells) becomes same as the page background, you feel "transparent" in Browser and not in Composer. I guess it's not a good idea to let user feel there are different color in Compposer and browser with same file, plus for N4.7 and 6.01 the table cell's background looks same in Composer and Browser.
verified in 3/27 build. ylong REOPEN if you still disagree...
Status: RESOLVED → VERIFIED
I think I need re-open it, cause it is really a Composer display problem. Like the comments that I added before, with same case, Browser and N4.7 / N6.01 don't display like that in Composer.
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
I was incorrect, this should be transparent and not opaque, if you save the file and bring it back into Composer, it renders correctly. If you change the document color, the table will render as opaque again. This is a rendering issue, reassigning to that component. Marc and I searched for any type of css setting that would be responsible for this, and we couldn't find one.
Component: Editor → Compositor
Wow, this is weird. What I don't understand is why cycling through HTML Source doesn't make the table transparent. That usually clears up display/layout problems and usually is the same as saving and reloading. Yung: why aren't your comments wrapping correctly? They are hard to read because they are so long!
The not wrapping long comments was might be a bug of N6.5, cause I added the comments using recently trunk build with this bugzilla application, which was automatically wrapping OK on N4.7.
really handing over to rendering
Assignee: beppe → kmcclusk
Status: REOPENED → NEW
QA Contact: sujay → petersen
Status: NEW → ASSIGNED
Target Milestone: --- → Future
There is a very similar case, I guess it's might be cause by same reason: On 04-12/04-16 trunk build, Edit | Preferences | Composer | New Page Settings, choose a image file for background, then click "OK" button. Open Composer, check the backgorund, you will find the background get "cut-off" - it only display a small part at the top of page, looks like it has not been load completely, but if you go check the HTML source or browser the page then back to the Editor page again, the background is a "complete" image.
I don't see the problem with 10/9/2001 build on WINNT. Marking WFM.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.