Closed Bug 54047 Opened 24 years ago Closed 20 years ago

XML Base not taken into account with :visited etc.

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: hjtoi-bugzilla, Assigned: dbaron)

References

()

Details

When we do the checking of if a link should be styled as visited or not, we do 
not take XML Base into account. (XML Base has been implemented so that if you 
mouse over a link or click it, the right thing will happen.) 

The spec for XML Base is at

http://www.w3.org/TR/xmlbase/

Right now the method that calculates XML Base is not exposed, so it is not 
possible to use it for style resolution. It would be simple to expose it, 
though. The problem is that the implementation is not fast enough for style 
resolution purposes: the XML Base is calculated on demand when the link is 
clicked/moused over.
Oops, my bug...

This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way 
-- please attach your concern to the bug for reconsideration.
Assignee: nisheeth → heikki
Target Milestone: --- → Future
This bug would also benefit from a well designed Link Manager.
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9
This doesn't seem to be too important, so moving to future again.
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9 → Future
XLINK related. Changing QA contact to bsharma@netscape.com
QA Contact: petersen → bsharma
Assignee: hjtoi-bugzilla → dbaron
Component: XML → Style System (CSS)
Priority: P3 → --
QA Contact: bsharma → ian
Target Milestone: Future → ---
Mm... lack of testcase.  This was fixed by bug 209573.  Adding testcase to URL
field.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Note bug 211916, which is why I tested with some random non-namespaced element
and had to hack around pretty-printing...
You need to log in before you can comment on or make changes to this bug.