firefox fails the Acid test?


Recommended Posts

isnt the acid test a verification or compliance test made by opera, or at least promoted by them, for internet browsers?

585766484[/snapback]

The original acid test was developed by the W3C as a way to test CSS1. The acid2 test was developed by the web standards project and opera (their browser fails :pinch: ) to test CSS2 (or was it 2.1).

Link to comment
Share on other sites

hehe.. every browser I tried failed, konq even tried to download something

Edit: Firefox doesn't do too badly.. it even animates the face, just hover over the 'nose' to see it

Link to comment
Share on other sites

hehe.. every browser I tried failed, konq even tried to download something

Edit: Firefox doesn't do too badly.. it even animates the face, just hover over the 'nose' to see it

585766616[/snapback]

It's not supposed to be animated lol :p

Link to comment
Share on other sites

The Acid2 test was created by the Web Standards Project (WaSP) and Opera Software ASA's Chief Technology Officer H?kon Wium Lie. Opera Software ASA played no part in the creation of the Acid2 test. H?kon Wium Lie participated as an individual, the individual which created CSS and still actively maintains the specifications. I believe that it is important for people to realize this because the misconception of Opera Software ASA being involved could create other misconceptions like the test not being fair when it truly is. Stick to your guns Panda lovers.

Also, the nose is supposed to change color when you hover over it, it's specified in the CSS. When you hover over the nose, it should turn blue. There is supposed to be another :hover effect which is applied to the :before and :after psuedo-selectors which makes their backgrounds inherit from the parent container, I haven't fully digested the code to figure out exactly what this does though. I will look into later.

After looking at the CSS, I noticed that they are not testing the ability to position, float, or display generated content on :hover. I will be sending an email to WaSP later about this because this is the greatest (imo) functionality in CSS 2.1. Although the functionality is not mentioned in the specifications, they should work together anyways because the :before and :after psuedo-selectors create actual elements in the DOM tree and thus, should have the same styling capabilities as conventional elements. The ability to :hover generated content and position it can open up many possibilities like interfaces which give hints at a predefined location or behave like normal tooltip windows. The ability to float generated content is also nice because we could use it for arrows on multi-level dropdown menu systems (use :after and give it the width/height of the arrow and use content: url('') to load the arrow image and then float it to the right so it aligns with the right side of the menu item.) I will probably also ask them to give an image which shows what the browser should render when the nose is hovered (I can't believe they created Acid2 with the intention of testing the ability to :hover but don't give any kind of success/failure indicator...) I doubt I will get any results from the e-mail, but it couldn't hurt to tr:yes:s:

Link to comment
Share on other sites

Is it about security flaw or just displaying the web content? I wonder if the attacker can take advantage of this problem.

Well, if all the browser fails who cares.

Link to comment
Share on other sites

Is it about security flaw or just displaying the web content? I wonder if the attacker can take advantage of this problem.

Well, if all the browser fails who cares.

585768927[/snapback]

It's about rendering CSS2 Features correct :)

Link to comment
Share on other sites

It's about rendering CSS2 Features correct :)

585768936[/snapback]

You mean a group of experts design a new standard without the client support? :huh:

We may wait for the new version of the browsers.

Link to comment
Share on other sites

You mean a group of experts design a new standard without the client support? :huh:

585769005[/snapback]

Well, it is hard for browser makers to implement the standard, if the people writing it are going to wait until the browsers support it to write it. :yes:

Edited by The_Decryptor
Link to comment
Share on other sites

You mean a group of experts design a new standard without the client support??

We may wait for the new version of the browsers.

The browser developers usually take part in writing the standards (Microsoft and Opera had assigned people as editors for the CSS 2.1 standard,) they just have a hard time sticking to their plans because the larger companies don't want to break backwards compatibility and/or are too lazy (Microsoft) and other companies (Opera, Mozilla, etc.) typically follow the standards as much as possible but have to follow some of the market-leader's (Microsoft) rendering behaviours to appear to "render correctly." This is why none of the browsers pass the Acid2 test, the Acid2 test is written according to the standards rather than stupid rendering bugs.

The Acid2 test was published to correct the mindset of browser developers so they will take advantage of their quirks mode (aka: page-errors mode) for backwards compatibility and use their strict mode (aka: correctly-written-page mode) for implementing the industry standard. And don't think that the Acid2 test was something that the W3C cooked up, it's really a big slap in the face from all of the unhappy web developers out there which haven't seen innovation for years and have had to cater to those same stupid rendering bugs for each browser. When all of the browsers render the same way, web developers only need to write their code and have it work on all browsers instead of having to test on 10+ browsers and hack around their individual rendering bugs (which leads to a lot of time wasted and time is money.)

I would also like to point out that the standard isn't new. CSS 2.1 has been a recommendation for around 14 months now and all of the browser/web developers knew of it for years while it was been created. CSS 3.0 is already beginning to reach maturity (expect average pages to drop in size by 20%, newspaper-style layouts where text flows from one column to another, alpha transparency on any element, round borders with or without images, etc.) and it won't be usable for another 7 years if browser developers don't kick it into gear and support standardization and common-interest innovation rather than proprietary solutions which only work in one browser.

The Acid2 test is a way to tell browser developers that web architects with a broader interest (read: don't intend on global market domination but would rather see technology improve in a way that is usable) should handle the progression of the web and that we're sick of waiting for them to look out for the people who make their browsers possible (the web developers.)

Link to comment
Share on other sites

I heard that the W3C are under pressure to remove standards that mainstream browsers don't implement. For example, the "text-shadow" style in CSS 2 was removed by CSS 2.1 because all browsers refused to implement it. It is now in CSS3. (FYI, Safari is the only browser that I know of, which does implement "text-shadow".)

Link to comment
Share on other sites

It's not supposed to be animated lol  :p

585768250[/snapback]

Its not supposed to animate. But the nose is supposed to change colour when you hover over it.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.