Uploader refactoring and opacity
Colin Clark
colin.clark at utoronto.ca
Mon May 12 15:00:47 UTC 2008
Hi Eli,
Interesting problem...
On 11-May-08, at 10:15 AM, Eli Cochran wrote:
> There is some code in Progress that does some tweaking to the format
> of the Progress dialog. There is a comment there now that the code
> should be moved to CSS. The reason the code is there is to make up
> for problems in CSS.
>
> Specifically that the opacity setting is browser specific. We can
> put it in CSS (and many people do) but then the CSS file will not
> validate, so when dealing with CSS, I usually let jQuery deal with
> it and handle the browser foo.
The general idea we were trying to encourage was that any appearance-
related settings are ideally expressed in CSS. Your point is that
opacity is specified in different ways depending on the browser. What
a drag!
So it seems like we have two possible options:
1. Expose opacity as a optional parameter in the JavaScript
2. Specify opacity value within the CSS in the W3C format but continue
to use jQuery to actually set the value
Any recommendations?
Colin
---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org