Closed
Bug 58501
Opened 24 years ago
Closed 24 years ago
Remove bogus instances of -moz-opacity
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla0.8
People
(Reporter: pierre, Assigned: mkaply)
References
Details
(Whiteboard: [easy fix][whitebox[)
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
This bug is extracted from bug 57307. See my comments from [2000-10-25 02:39] and
[2000-10-26 18:25].
We should remove all the cases where the opacity is set to 99%. It makes no
sense and I imagine it can only use more CPU power than having opacity set to
100%.
Reporter | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [easy fix]
Target Milestone: --- → mozilla0.6
Reporter | ||
Comment 1•24 years ago
|
||
See bug 58517 about ekrock's suggestion to the name of the property.
Depends on: 58517
Reporter | ||
Updated•24 years ago
|
Target Milestone: mozilla0.6 → mozilla0.8
Comment 2•24 years ago
|
||
got the patch?
should we take it for m0.8 to get some testing
or performance kick?
if not, then change the milestone.
Assignee | ||
Comment 4•24 years ago
|
||
The only places where opacity is set to .99 is in the image map editor.
Removing these lines from image map editor makes image map editor work on OS/2
since we don't support opacity yet.
We will be attaching a diff in a minute and humbly begging to get this into .8.
We just realized that this was a problem on OS/2 this morning.
Assignee | ||
Comment 5•24 years ago
|
||
Comment 7•24 years ago
|
||
r=brade
Reporter | ||
Comment 8•24 years ago
|
||
Back to moz0.8 + reassigned to Michael who's got the fix and a CVS account.
Ask ben@netscape.com or sfraser@netscape.com for approval.
Assignee: pierre → mkaply
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9 → mozilla0.8
Comment 9•24 years ago
|
||
cmanske, brade: do we know why the image editor used opacity of .99 everywhere?
Comment 10•24 years ago
|
||
It was only being used in one place to "wash out" the image for the High
Contrast feature. This feature is now soon to be taken out as it was not
functioning anyway.
Comment 11•24 years ago
|
||
mkaply, is this something you're interested in getting in for 0.8?
Assignee | ||
Comment 12•24 years ago
|
||
Asa. Yes definitely. I was waiting for an sr= so I could send it to drivers.
Without this fix, the hotspot editor doesn't work on OS/2.
Updated•24 years ago
|
Whiteboard: [easy fix] → [easy fix] critical to 0.8 for OS/2
Comment 13•24 years ago
|
||
sr=sfraser
Comment 14•24 years ago
|
||
a=asa for checkin on the 0.8 branch
Assignee | ||
Comment 15•24 years ago
|
||
Fix checked in on branch.
Leaving open until trunk opens so I can get it on the trunk.
Status: NEW → ASSIGNED
Updated•24 years ago
|
Whiteboard: [easy fix] critical to 0.8 for OS/2 → [easy fix]
Comment 16•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking
remaining non-tables style bugs. Sorry about the spam. I tried to get this done
directly at the database level, but apparently that is "not easy because of the
shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
Assignee | ||
Comment 17•24 years ago
|
||
Fix checked in to trunk
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 18•23 years ago
|
||
We finally have the explanation as of why someone set the opacity to 99% in the
ImageMap Editor files... See bug 92282: when the opacity is 100%, we can't
change it dynamically; when it is 99%, we can.
Updated•22 years ago
|
Whiteboard: [easy fix] → [easy fix][whitebox[
You need to log in
before you can comment on or make changes to this bug.
Description
•