Forum: Radiant CMS CSS Bugs (mixed in with IE)

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Chris P. (Guest)
on 2007-04-14 08:58
Well I'm done just lurking and have finally begun working with radiant.
Like it.

On this project, we've had to modify the edit_page.rhtml to add some
fields. I ran into issues when trying to stylize these elements

First of all, the CSS problems don't seem to be limited to IE (I'm
testing with 6 right now).  I also get some odd results using Firefox
and Opera.

I'm seeing two distinct issues:
1.) The .fieldset tables (within the div.extended_metadata) is set to
choose some odd widths for the columns with input textboxes.  Right now
the textbox width is derived from a weird combination of the 100% style
and the maxlength property.  Actually, this looks fine on the default
edit_page using Firefox but add a text box with a greater maxlength
(currently the largest is 160 characters) and watch what happens.  And
even Firefox shows this odd behavior on the default edit_layout page
(click "more" for content-type).

Opera shows all these oddly but IE 6 really goes bonkers with this one -
sending the textboxes off the edge of the screen.  Though, in this case
I don't fully blame IE - the applied styles here are a bit, well,
interesting.

2.) I'm not even sure what to call this issue (reminds me of the good
'ol IE peekaboo bug).  When you load the edit_page page, the title label
(the one that says "Page Title") is not shown.  Try to select the text
or maybe scroll just the right way, and it suddenly appears.

The 2nd problem is all IE but is also easy to fix (one added line).  The
first one is a bigger change (actually it looks like the main.css could
use some spring cleaning).

So, I'd be happy to contribute here but I don't want to duplicate work
that is maybe already being done.  I also don't want to spend a lot of
time only to learn that something like the facets branch is going to
obliterate my work.

Let me know how/if you want some help here.

-Chris P.
John W. Long (Guest)
on 2007-04-14 11:47
(Received via mailing list)
Chris P. wrote:
> So, I'd be happy to contribute here but I don't want to duplicate work
> that is maybe already being done.  I also don't want to spend a lot of
> time only to learn that something like the facets branch is going to
> obliterate my work.
>
> Let me know how/if you want some help here.

A separate patch for each of these issues would be very helpful. I'm not
personally very concerned about Opera, but I would love to improve the
IE 6 & 7 support.

--
John L.
http://wiseheartdesign.com
Chris P. (Guest)
on 2007-04-14 21:02
Happy to.

Is there anyone intimately familiar with main.css?  There are a few
elements that look to be remnants from earlier stylings (like they once
applied to this issue but now don't do anything). I'd like to clean
those up too but I'd hate to learn that some "secret" page somewhere
needs them.

Anyway, it would help if someone was available to ask questions like
"what's the story behind this?"  Unlike ruby, CSS is ghastly to read and
decipher.
John W. Long (Guest)
on 2007-04-17 06:58
(Received via mailing list)
Chris P. wrote:
> Is there anyone intimately familiar with main.css?  There are a few
> elements that look to be remnants from earlier stylings (like they once
> applied to this issue but now don't do anything). I'd like to clean
> those up too but I'd hate to learn that some "secret" page somewhere
> needs them.

You are welcome to contact me directly with questions about the CSS. I
just checked in some changes which should fix the two main bugs on IE 6
on the page edit screen. Can you verify?

--
John L.
http://wiseheartdesign.com
This topic is locked and can not be replied to.