"If I used an API in some version and it used to work, I consider it a bug that it does not work in new releases."
Such is only true if the implementation (firefox) of the API (css) contains no bugs at all.
Your use of the API should be based on the API itself (css rules), not on what seems right in some implementation (firefox) and your problem is caused by 'programming' against the Firefox implementation of the CSS API, rather than writing your website according to CSS (API) rules.
The Firefox implementation of CSS had bugs (I don't know of CSS implementations that are bug-free) that are fixed in this new release. You only needed to change your website because you were exploiting the fact that Firefox did not implement the API correctly.
I'm afraid you should not blame Firefox for incompatible changes but rather blame yourself for programming against an implementation in stead of programming against the (strictly defined!) API.
Follow
"If I used an API in some version and it used to work, I consider it a bug that it does not work in new releases."
Such is only true if the implementation (firefox) of the API (css) contains no bugs at all.
Your use of the API should be based on the API itself (css rules), not on what seems right in some implementation (firefox) and your problem is caused by 'programming' against the Firefox implementation of the CSS API, rather than writing your website according to CSS (API) rules.
The Firefox implementation of CSS had bugs (I don't know of CSS implementations that are bug-free) that are fixed in this new release. You only needed to change your website because you were exploiting the fact that Firefox did not implement the API correctly.
I'm afraid you should not blame Firefox for incompatible changes but rather blame yourself for programming against an implementation in stead of programming against the (strictly defined!) API.
--Rijk van Haaften 22:21, 11 February 2009 (CET)