MK wrote:
> On 06/09/2009 05:02:01 PM, Jonathan Swartz wrote:
>
>> Hi MK,
>>
>> All the problems you describe are occurring on the client (browser)
>> side. The browser is solely responsible for intrepreting HTML & CSS.
>>
>
> I guess you are correct!
>
> Looking at the page source, I realized it will be a stupendous mistake
> to try including some (potentially) monster string with tons of mark-up
> as a content argument to a js function. So I got around that with
> Ajax.Updater...ajax is a new thing to me as well.
>
> The only issue this does not solve is this one:
>
> .mini { font-size: small; color: #bbbbbb; }
> p.mini:hover { color: #ffff00; }
> .link { text-decoration: none; }
> p.link:hover { color: #ffff00; }
>
> I am certian I have not had to do this (add the "p") to get a hover to
> work before. Looking at the page source, obviously, does not provide a
> clue. This one issue is almost inconsequential, but any thoughts?
>
I have found the firebug add-on for firefox to be invaluable when
debugging client side (css/js) issues. That could help point out which
aspect of the differing sources is causing the difference in rendering.
RJ Herrick
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
