Bug Tracker

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#10054 closed bug (wontfix)

Loading of library near closing <body> tag produces CSS validation errors

Reported by: dan.bower88@… Owned by:
Priority: low Milestone: 1.6.3
Component: misc Version: 1.6.2
Keywords: Cc:
Blocked by: Blocking:

Description

Hey,

I'm not entirely sure if this is a FF 5.0 issue or a jQuery issue but I am experiencing the following.

  • http://jsfiddle.net/TUSMq/ - Produces CSS validation errors. This information is obtained from the Web Developer add-on for Firefox. I'm also running Firebug but I don't think it has any involvement in this.
  • http://jsfiddle.net/TUSMq/1/ - Does not produce CSS validation errors. The only difference is that 1.6.1 is loaded instead of 1.6.2.
  • http://jsfiddle.net/TUSMq/3/ - Does not produce CSS validation errors. This differs from the first fiddle in that the <script> element is a child of <head> instead of <body>.

The CSS validation errors are:

  • "Error in parsing value for 'left'. Declaration dropped"
  • "Error in parsing value for 'right'. Declaration dropped"

Sorry if this in indeed a problem for FireFox but even if it is, it may be more appropriate if they're notified from you instead of some random noob :) Hope it helps

Change History (3)

comment:1 Changed 8 years ago by Rick Waldron

Component: unfiledmisc
Milestone: None1.6.3
Priority: undecidedlow
Resolution: wontfix
Status: newclosed

jsFiddle automatically wraps markup from the HTML box with <html>, <head> and <body>, so your examples are actually all invalid. Additionally, these CSS errors are extraneous.

comment:2 in reply to:  1 Changed 8 years ago by anonymous

Replying to rwaldron:

jsFiddle automatically wraps markup from the HTML box with <html>, <head> and <body>, so your examples are actually all invalid. Additionally, these CSS errors are extraneous.

I am sorry, I was simply using jsFiddle as a place to paste the HTML. I was conducting the tests from the local server. 1.6.2 is doing something that triggers invalid CSS. It's certainly doing something that 1.6.1 is not. Someone I have spoke with has reproduced this error. Please don't ignore it.

comment:3 Changed 8 years ago by anonymous

I am also encountering the same problem with all web pages generated using jQuery version 1.6.2. The errors disappear upon downgrading to 1.6.1. Definitely a bug.

Note: See TracTickets for help on using tickets.