308514 - Error: Error in parsing value for property 'cursor'. Declaration dropped. Source File: about:blank Line: 0 (Blogger live bookmark)

Status: RESOLVED WORKSFORME

(Firefox :: Bookmarks & History, defect)

Description

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050914
Firefox/1.4 ID:2005091407

My JSC gets constantly filled with the error as in summary

Cause is the loading of live bookmarks

repro:
1.Open FF
2.Open JSC
3.if livebookmarks haven't automatically loaded JSC should be empty, else you'll
see a pack of these errors.
4.rightclick on any live bookmark and select "Reload Live Bookmark"
5.See another bunch of these errors appear in JSC.

(I'll try to figure out a regressiondate/time if i can find some spare time)

Comment 1

[Peter van der Woude [:Peter6]]

-safemode made no difference

tried it back till the 20050401 build and it still throws that error

Comment 2

[Ria Klaassen (not reading all bugmail)]

Nope. Sometimes a system restart can do miracles. :)

Comment 3

[Peter van der Woude [:Peter6]]

gotcha....

repro:
1. Open FF
2. Go to http://ikkwamikzag.blogspot.com/ (my Blog)
3. add the live bookmark to your bookmarks
4. select the live bookmark (in BM or bookmarks menu or bookmarks toolbar) and
rightclick refresh.
5. check out JSC and see the errors.

Comment 4

[Phil Ringnalda (:philor)]

6. ROFL, because it's Peter's own (yeah, I know Blogger adds it automatically)
invalid markup throwing the errors.

So, what's the expected behavior? Not parse the contents of Atom <content>
elements with inline XHTML, because we don't actually use them? Tell the parser
the URL of what it's parsing, so the errors will all point to
http://ikkwamikzag.blogspot.com/atom.xml rather than about:blank?

Comment 5

[Phil Ringnalda (:philor)]

Peter? What was your expected result? If it was "report the correct origin of the CSS bugs, rather than about:blank" then it now WFM: the fixes for relative URLs involved telling the parser what URL we're parsing, so now they are just the exact same errors that loading the HTML produces. If it was "tell the parser not to report CSS errors in inline XHTML" then... Rob, is that possible?

Comment 6

[Peter van der Woude [:Peter6]]

(In reply to comment #5)
> Peter? What was your expected result? If it was "report the correct origin of
> the CSS bugs, rather than about:blank" 
>
This one

Comment 7

[Robert Sayre]

(In reply to comment #5)
>
>If it was "tell the
> parser not to report CSS errors in inline XHTML" then... Rob, is that possible?

I don't think the new feed service will do this.