guest
|
| Posted: 03/05/2002, 12:23 PM |
|
Is it by intentional codecharge design that for PHP+templates/CSS code
for MENU URL items, the generated <A> tags surround the generated <font>
tags>. eg:
<td class="DataTD"><a href="faq.php"><fontclass="DataFONT">FAQ</font></a></td>
instead of what we would get (the reverse) if we "handcode" the link:
<td class="DataTD"><fontclass="DataFONT"><a href="faq.php">FAQ</a></font></td>
Resulting treatment of the text as a "link" seems to differ
dramtaically between the two approaches (observed for browsers: NS4.7x,
MSIE5.x and Opera 5.x/6.x). It would seem that "DataFONT" overrides some of
the the normal link presentation such as link color.
Although it might look "cooler"/"cleaner" in some cases not to have
link treatment, it would seem to me that this is a design imperative. I would
either either have the option or have it done the second way when generated
and leave the design control to CSS etc. My guess is that this is a bug!
TIA,
- Don
PS: Codecharge support: I don't visit the web based forum, please pass this
along for me.
|
|
|
 |
CodeCharge Support
|
| Posted: 03/05/2002, 4:01 PM |
|
Both the <A> and <font> tags are inline elements and can be nested in either
order. Regardless of how you nest the tags, how they ultimately render
depends on the user agent.
CodeCharge Support.
<codecharge@deliberate.net> wrote in message
news:og9a8ug9jth3cpn4coj2rvr8npv368jkp0@news.codecharge.com...
>
> Is it by intentional codecharge design that for PHP+templates/CSS code
> for MENU URL items, the generated <A> tags surround the generated <font>
> tags>. eg:
>
> <td class="DataTD"><a
href="faq.php"><fontclass="DataFONT">FAQ</font></a></td>
>
> instead of what we would get (the reverse) if we "handcode" the link:
>
> <td class="DataTD"><fontclass="DataFONT"><a
href="faq.php">FAQ</a></font></td>
>
> Resulting treatment of the text as a "link" seems to differ
> dramtaically between the two approaches (observed for browsers: NS4.7x,
> MSIE5.x and Opera 5.x/6.x). It would seem that "DataFONT" overrides some
of
> the the normal link presentation such as link color.
>
> Although it might look "cooler"/"cleaner" in some cases not to have
> link treatment, it would seem to me that this is a design imperative. I
would
> either either have the option or have it done the second way when
generated
> and leave the design control to CSS etc. My guess is that this is a bug!
>
> TIA,
>
> - Don
>
> PS: Codecharge support: I don't visit the web based forum, please pass
this
> along for me.
|
|
|
|
guest
|
| Posted: 03/06/2002, 8:37 AM |
|
In codecharge.discussion, "CodeCharge Support" <Walkerp@codecharge.com> wrote:
=> Both the <A> and <font> tags are inline elements
Of course.
=> and can be nested in either order.
And the order of nesting effects output. And the nesting is
*generated* by CodeCharge.
=> Regardless of how you nest the tags, how they ultimately render
=> depends on the user agent.
Of course, what you write above is somewhat true, but it doesn't
really address the point in question. BTW: a Codecharge user has *no* control
over that order of use in generated code.
The point is: in "URL"s, Codecharge puts the <font> tages inside of
the <a> tages, which causes the formatting associated with the <font> tags to
override, in part, the normal <a> formatting.
This becomes apparent in contrast when one attempts to "handcode" a
URL into a menu item as there the <font> tages are on the outisde of the <a>
and allow the links normal formatting, such as visited/non-visited, hover
effect (CSS2), etc. {Try it and see].
My apologies for pressing the point, but this would seem to be a
CodeCharge bug, IMHO.
Cheers,
- Don
PS: Codecharge support: I don't visit the web based forum, please pass this
along for me.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=> <codecharge@deliberate.net> wrote in message
=>news:og9a8ug9jth3cpn4coj2rvr8npv368jkp0@news.codecharge.com...
=> >
=> > Is it by intentional codecharge design that for PHP+templates/CSS code
=> > for MENU URL items, the generated <A> tags surround the generated <font>
=> > tags>. eg:
=> >
=> > <td class="DataTD"><a
=> href="faq.php"><fontclass="DataFONT">FAQ</font></a></td>
=> >
=> > instead of what we would get (the reverse) if we "handcode" the link:
=> >
=> > <td class="DataTD"><fontclass="DataFONT"><a
=> href="faq.php">FAQ</a></font></td>
=> >
=> > Resulting treatment of the text as a "link" seems to differ
=> > dramtaically between the two approaches (observed for browsers: NS4.7x,
=> > MSIE5.x and Opera 5.x/6.x). It would seem that "DataFONT" overrides some
=> of
=> > the the normal link presentation such as link color.
=> >
=> > Although it might look "cooler"/"cleaner" in some cases not to have
=> > link treatment, it would seem to me that this is a design imperative. I
=> would
=> > either either have the option or have it done the second way when
=> generated
=> > and leave the design control to CSS etc. My guess is that this is a bug!
=> >
=> > TIA,
=> >
=> > - Don
=> >
=> > PS: Codecharge support: I don't visit the web based forum, please pass
=> this
=> > along for me.
=>
|
|
|
|
|
