Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
Bartik theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Dec 2010 at 08:40 UTC
Updated:
18 Jan 2011 at 05:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
Jeff Burnz commenteddang it, status...
Comment #3
Jeff Burnz commentedFailure is real, forgot to add back the default color for text, which coincidentally is the same color used in the test. Good catch color test!
Comment #4
Tor Arne Thune commentedThis is something I would really like to see implemented, as I have encountered this using TinyMCE. Subscribing.
Comment #5
jensimmons commentedWait... what?
We've debated body background color for a long time, in multiple issues.... tried sticky footer. Decided not to do sticky footer. Went with min-height.... etc. All to keep WYSIWYG happy. And not putting the footer color on body — instead putting the overall page color on body... and now it needs to be changed again?
Jeff can you explain what you are wanting to do in the context of all the other many debates we've had.
(/me now hates WSYIWYG editors more than ever.)
Comment #6
dcrocks commentedI really don't agree with this and I think the future intends us to stop ignoring the html and body elements as layout and styling targets. Maybe it is time for the wysiwig editors to clean up their acts and get with it. I don't intend to build any theme that cater to dysfunctional wysiwig editors, even if it means my themes aren't usable to others.
Comment #7
Jeff Burnz commentedWe've had a number of fixes added for the footer/background issue and each one of them has resulted in new issues being created. With the background on BODY we have an issue for many Drupal users (200000+ Drupal sites (over 55%) use an editor), not to mention other uses of iframe loaded documents/widgets etc.
I know HTML and BODY elements are very useful, I suppose it just depends if you care about the rather large amount of users who will be affected by this, the fix is pretty simple really, not sure what the objection is?
We just committed a fix to support Panels, certainly far fewer sites use Panels than use an editor, I didn't see any objections in that issue.
Comment #8
amateescu commentedI'm not familiar with the background of this issue, but I have to agree with Jeff here.
I always go to my editor configuration page and force it to use its default css, but how many users know how to do that?
Maybe we should bring this up in their respective issue queues and ask if they are willing to set the defaults to whatever css comes with the editor.
Comment #9
jensimmons commentedYeah, while I agree with the frustration expressed by dcrocks in comment #6, I do think Bartik must support WYSIWYG editors. We just have to. We can't expect users to configure their site in a obscure way so that we can have some kind of code purity on our part. (And it's not really an issue of code purity anyway.)
So let's make sure Bartik works with WYSIWYG editors.
Comment #10
jensimmons commentedpatch fails to apply :(
Comment #11
jensimmons commentedTalking about this in IRC, I realize, I'm simply confused about what we decided to do about background colors and wysiwyg editors. I though we'd already fixed this issue. And now, here is another issue claiming that how it is now is wrong, and it needs to be changed in yet another different way.
Before we make anymore changes, I'd like someone to write up a summary of what's been going on / explain why the way it is now is not ok (despite all the previous discussions and decisions), and why the new change is better. Of course, it's too much work to do an exhaustive history. That's too much. But a brief explanation is needed I think — at least for those of us who are totally confused at this point about why past fixes haven't stuck.
Comment #12
Jeff Burnz commentedPatch needs a re-roll since another patch was committed. If you want this as the fix to the issue then please do so, I've done my bit here and run out of time for this issue.
Jen - there is a full historical account of all changes made in CVS.
Comment #13
tim.plunkettThe rich history of this debate is NOT clear from CVS, because most of the discussion resulted in patches not getting committed. The body{background-color:#fff;} in style.css is from v1.1, and the body{background-color:#292929;} is from when I changed it from #2d1e0f back in #879536: Improve Bartik's "Blue Lagoon" color scheme. Not very helpful.
Currently, the body background matches the #footer-wrapper background, to enable the faux-sticky-footer effect we have going on. The patch looks like it addresses that, which is my main worry.
If anyone else remembers the several other reasons we debated about changing this, please chime in.
Comment #14
Jeff Burnz commentedLook in CVS (both for D7 core and Bartik contrib) you can find where the changes were made and use the #issue numbers to look up the relevant discussions.
Heres an alternative, NOT one I am totally happy with but could be a solution - however it special cases for the WYSIWYG module, so if user is not using this module they're shit out of luck... but it does avoid the rather hacky workaround in #3. I will stress again, this is only an idea, need some committer feedback, and if sun is around he might have a better idea...
Comment #15
tim.plunkettThis is a reroll of Jeff's patch from #3. I really think it is the best solution.
Needs one other pair of eyes, but I think it's RTBC.
Comment #16
jody lynnPatch looks good to me in Chrome, Safari and Firefox and it solves my problem in #1013606: Text in region-page-top and region-page-bottom is white on white.
Not marking RTBC until tested in IE.
Comment #17
neclimdulLooks fine for me in IE6-8
Comment #18
webchickHm. Given the very strong opinions earlier that were totally anti-this patch, I feel like this could use some more review.
Comment #19
tim.plunkettJeff has been right since the beginning. I missed some of the history in the contrib->core switch. Any dissenting opinion of mine was uninformed.
The patch moves the dark background and light font color out of and also preserves the faux-sticky-footer.
Comment #20
Jeff Burnz commentedI think most the objections were from misunderstanding the issue and what we have done over time with regards to the footer and body elements. This is quite understandable, we have messed around this a few times, but inadvertently created new issues in the process. I would love to summarize the changes however I don't have so much time right now.
What I can do is explain what this patch does, blow by blow. Its actually pretty simple stuff and really does fix the issue.
First this switches the body background from #292929 (dark gray) to white. Second it changes the default color for text from white to #3b3b3b (dark gray).
These are the key changes for WYSIWYG editor support and other issues such as the page-top/page-bottom white on white issue.
This sets the dark gray background on the #page-wrapper as opposed to the body element - this is for the "expanding sticky footer" emulation. Before we used the body element because it automagically expands to full height of the viewport, and a DIV won't do this normally, so we need the next bit of code...
This is the key to the #page-wrapper with background color actually working, we trigger 100% height on this element so the background always fills up the whole page - creating the illusion of an "expanding sticky footer".
This adds the white background to the #page and #main-wrapper wrapper divs - the white bit between the header and the footer,
Powered by Dreditor.
Comment #21
webchickOk, thanks for the expanded explanation. My CSS-fu has gone way downhill since starting with Drupal. :)
Committed to HEAD.