Recommended Posts

http://my.opera.com/desktopteam/blog/2008/...-the-acid3-test

Opera and the Acid3 Test

We have some excellent news! Lars Erik Bolstad, the Head of Core Technology at Opera Software, sent me the following information to share:

acid3_100.png

I have a quick update on where we are with Acid3.

Since the test was officially announced recently, our Core developers have been hard at work fixing bugs and adding the missing standards support.

Today we reached a 100% pass rate for the first time! There are some remaining issues yet to be fixed, but we hope to have those sorted out shortly.

We will release a technical preview version on labs.opera.com within the next week or so. For now, the screenshot above shows the Acid3 test as rendered in our latest WinGogi Desktop build. WinGogi is the Windows version of our reference builds used for the internal testing of Opera's platform independent Core.

Opera came out of nowhere! Some of the new things you can do with CSS are very cool IMO.

It didn't come out of nowhere... they were just working on Acid3 separately from the regular Kestrel builds, hence their post-Kestrel builds passed. There was also probably much secrecy involved so that the others wouldn't work harder. :p

The Firefox nightlies don't seem to be improving at all anymore.... I guess webkit is the only browser with a full focus on Acid3.

Somehow, these tests seem to always show up when Firefox is near the end of a development cycle in Gecko; It's not really Mozilla's fault, it's just unfortunate.

They've pretty much fixed what they can for fx3, anything else is going to need to involve bigger (destabilizing) changes.

It'd be cool if this whole entire time, the team at Mozilla has been working their butts off on Acid3 and release the nightly that scores 100 like right before WebKit does. That would be freakin sweet.

Everything Mozilla does is public. That's why unusable developmental builds get so many pointless threads started for them.

I'm not convinced that Acid tests are really useful in the real world. Don't get me wrong, I support standards, but it seems the Acid test purposely tests the areas that the browsers will interpret differently rather than the areas that are most commonly used in web design.

I'm currently working on a fairly complicated design, and so far it renders near perfectly in FF, Opera and IE5-7 with only 2 "* html" bits in my CSS. I personally think that if you are needing hundreds of hacks, you're doing something wrong (or plain lazy, which I've come to realise is very common amongst web designers/developers).

Even if standards were applied flawlessly across all browsers, some things (fonts) will never be the same across all browsers and all systems.

The text-shadow property used in Acid3 would be the first cross-browser supported way to display shadow under text, actually. It is a really cool addiction.

firefox devs have pretty much written off acid 3. they did the same thing with acid 2. probably won't see it completely supported till firefox 4. a real shame.

So true since it's such a popular browser. Of course IE is even larger but we all know it won't pass Acid 3 for a while.

http://ln.hixie.ch/?start=1206578003&count=1

Last minute change to Acid3 (test wasn't in line with the standards)

This was posted after Opera hit 100/100, and before Safari hit 100/100, So is Opera back on 99/100 (It should be, since the test was wrong)

And the Firefox guys didn't "write off" Acid2, it required fairly large changes to the rendering engine (look up the reflow branch)

firefox devs have pretty much written off acid 3. they did the same thing with acid 2. probably won't see it completely supported till firefox 4. a real shame.

Would you really rather them push back fx3's release another 2 or 3 months?

Even when the current release branch (fx2) still doesn't pass acid 2? :wacko:

-----------------------------------------------------

Honestly, for a development team to spend all their time racing to be the first push an unofficial release to pass an acid test is kind of stupid.

Passing the test is supposed to be an indicator of how robust a job the rendering engine does overall. If you are racing to patch acid test specific bugs, you're destroying the point of the test in the first place.

Would you really rather them push back fx3's release another 2 or 3 months?
Personally I'd like to see them get 3.0 out soonish and then look at having acid support in a "soon after" release, something like 3.2 or 3.5 or whatever they go to after 3. That or get 4.0 out within 9 months. I dont want acid 3 to delay ffx 3 now, but it's be nice if it didnt take too long for them to support it (or at least 90+%).
Nobody has passed the test yet.

I mean, do you actually checked the link I just posted? Because I did, and I just tried the Acid3 test and it passed...

In case you missed the direct link, http://nightly.webkit.org/

Unless you mean like in some sort of subliminal way...

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

    • No registered users viewing this page.
  • Posts

    • Qwen 3.6 is better value per dollar, and you can run it locally for free.
    • I don't believe them that anyone using threads, at least meaningfully. It's the same thing for Facebook, people just don't engage with Meta platforms like they are thinking. This isn't 2006.
    • Not taking AI slop on the go with me, hard pass for me.
    • Same Internet Archive seemed to grab the new version https://web.archive.org/web/20...d/Setup_MakeMKV_v1.18.4.exe Here's the link to an additional file it periodically downloads https://web.archive.org/web/20260213092148/https://www.makemkv.com/sdf.bin I think update's keys, etc. To manually trigger this update, put the sdf.bin file in the root of where the program is installed. When you launch the program it will pick up the file and import it. Typically put it here: C:\Program Files (x86)\MakeMKV\sdf.bin
    • Windows 11 KB5094126, KB5093998 bugging out Office apps but it may not be Microsoft's fault by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. Although the tech giant did not acknowledge any major problems, some users online reported various issues ranging from OneDrive and Dropbox access problems, BitLocker recovery lockouts, to blue screens and BSODs. You can read about them in this dedicated piece. While there is still no confirmation about those problems from Microsoft the company has admitted to another bug which we did not report on. The tech giant has confirmed it has received reports of an issue in which certain third-party applications may be unable to launch Microsoft Office apps or open Office documents after installing the Patch Tuesday. This affects both Windows 11 as well as Windows 10. The company says the problem impacts a subset of applications that rely on OLE (Object Linking and Embedding) automation to communicate with Microsoft Office programs. According to Microsoft, affected scenarios involve third-party software attempting to open Office applications or documents from within their own interface. In such cases, the Office program may fail to launch altogether, or the requested document may not open. Oddly there may not be any error message, which probably makes the issue difficult to diagnose. The bug affects several Office products, including Word, Excel, PowerPoint, Access, and other apps in the Microsoft Office suite when they are launched through the affected software. These include tax and accounting software such as CCH Engagement and Workpaper Manager, dental practice management solutions like Dentrix and Softdent, as well as the popular research and reference management tool Zotero. Microsoft adds that other applications using similar Office integration methods could also experience the same problematic behavior. To understand the issue it is important to look at OLE, the Microsoft technology involved. OLE allows different applications to work together and share data, while its Automation feature lets one program control another. Thus this enables third-party software to launch Microsoft Office apps, open documents, and perform tasks automatically without requiring users to switch between programs. Because many accounting, healthcare, research, and business applications rely on OLE automation to interact with Word, Excel, PowerPoint, and other Office apps, any disruption can break those workflows. As a result, affected software may be unable to open Office documents or launch Office applications even though the programs themselves continue to work normally. At the moment the company has not provided a permanent fix though it has confirmed that engineers are actively working on a resolution, which will be delivered through a future Windows update. As such additional details will be shared once more information becomes available. In the meantime, Microsoft recommends a simple workaround for affected users whic is to open the Office application or document directly rather than launching it through the third-party program. For enterprise customers and organizations managing larger deployments, Microsoft says an additional mitigation is available. Admins experiencing the problem on their managed devices are advised to contact Microsoft Support for business to obtain and apply the workaround.
  • Recent Achievements

    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!