Bug Tracker

#13569 closed bug (cantfix)

Opened March 05, 2013 08:46PM UTC

Closed March 05, 2013 10:22PM UTC

Last modified December 22, 2013 07:23AM UTC

Unknown property 'box-sizing'. Declaration dropped.

Reported by: unveiled14@gmail.com Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.9.1
Keywords: Cc:
Blocked by: Blocking:
Description

Warning in Firefox console appears on page load when jquery is included. To recreate: include jquery in an otherwise empty html file and open in Firefox (19.0). Doesn't break anything, but it's annoying for a library to generate warnings that don't indicate that they originate from the library.

Attachments (0)
Change History (5)

Changed March 05, 2013 10:22PM UTC by dmethvin comment:1

resolution: → cantfix
status: new → closed

The CSS box-sizing property is real. Firefox should not warn about it. Please don't let the anal retentive crowd turn this into another #7535. Complaints can either go to /dev/null or here: https://bugzilla.mozilla.org/show_bug.cgi?id=243412

Changed March 06, 2013 08:45PM UTC by m_gol comment:2

Yeah; unfortunately, Mozilla people seem to think box-sizing is a bad idea (I strongly disagree, happily using * {box-sizing: border-box;} on my sites) and they don't IMHO pay enough attention to fixing its issues and removing the prefix.

There's not much we can do about it, though.

Also, if we paid attention to such warnings, we would be killed by Opera that complains about every single vendor prefixed property it doesn't recognize (and why should it? it's vendor prefixed, for Christ's sake!).

Changed April 04, 2013 04:33AM UTC by m_gol comment:3

#13707 is a duplicate of this ticket.

Changed July 24, 2013 09:21PM UTC by anonymous comment:4 

I strongly disagree, happily using * {box-sizing: border-box;} on my sites

Your strong disagreement doesn't count for much if you're using that css ''anywhere'' under any circumstances.

Changed December 22, 2013 07:23AM UTC by anonymous comment:5

Just pinging to say that after 9 & 1/2 years, the FF bug responsible for this looks to be only a few more months (optimistically, weeks?) away!