Slashdot Mirror
Konqueror Passes the Acid2 Test Too
An anonymous reader writes "A month after Safari , and after a lot of controversy, Allan Sandfeld Jensen announced today that Konqueror passes the Acid2 test too. Half of the patches could be merged from Apple's Webcore, the rest needed to be rewritten from scratch."
Sorry, dont know what that is. Could someone post a link...
"Allan Sandfeld Jensen announced today that Konqueror passes the Acid2 test too. Half of the patches could be merged from Apple's Webcore, the rest needed to be rewritten from scratch.""
It's amazing what people can do when sufficiently motivated.
Can someone tell any more news on whether KDE people are successful getting Apple to release their code properly? I know they obviously can use part of the code like they have here, as they have done some of it and pass the Acid2 test.
Is that enough under the GPL? shouldn't Apple be doing more?
I for one am very glad that the Gecko/Mozill engine is not our only choice in free software based renderers. There is some security in seeing that we have at least two projects with excellent browsers available for the community.
Congrats Konqueror team!
I wonder if anyone is working on a Windows port of this?
Throw the bums out!
I have been using Konqueror a bit more that usual recently because it loads quicker that Firefox, and I still find myself switching to Fx for pages that render wrong
# cat
Damn, my RAM is full of llamas.
What the hell is Acid2? What does it have to do with Safari/Konqueror? What patches? Apple's Webcore? What's that?
This is where editors are supposed to come in. There's no point in posting a story to the front page that only the 10 people who use konqueror are going to understand.
Both Safari and Konqueror have improved because of Open Source. Even though the two teams worked independently, they benefited from having access to the other's code.
Does it really matter what Apple's motivations were? The end result is that Open Source development has helped both products.
I'll probably be modded down for this...
...acid drops YOU!
See my G5 baby pictures
Now we are waiting for IE to support the ACID2 test.
And only then, we could design web sites using today's CSS features. Oh, not today's, 5 years ago's but it will still be a revolution.
{{.sig}}
KDE is aweful to use though. I hate it so much. Gnome is far better, but I doubt this version of KDE will be in debian's stable for some time yet, and by that time Debian will have pointed out many bugs.
Whats the big deal? just wait for the debian guys to approve something, its more worthy a test than acid.
Why UNIX?
I think it's great that the KHTML team have managed to pass the ACID2 test only a month behind Apple. However, I am skeptical if this kind of pace can be continued in the future. Firstly, it looks like the KHTML developers might have been working harder than usual just to pass the test so that they wouldn't lose face. As the two code bases diverge (they only merged half of Apple's patches) it will become increasingly difficult for the KHTML guys to keep up. Webcore is effectively a fork, and there's a diminishing degree to which code can be shared between the fork and the original.
Unless KHTML receives extra resources (in money, developers, etc.), I fear that they may be left behind Mozilla and Webcore.
OLPC Australia
This is a site for geeks, and most readers are regular readers.
The Acid2 test is not something specific to konqueror, it's a test for browsers in general, it has been covered here a lot lately, just search, or read the site more often.
Safari is based on Konqueror, Apple publishes it modifications of Safari and people tries to backport the useful ones to Konqueror. There has been troubles about this, since apple does a few things that make it hard to reuse the code, again, you are either trolling, or you really don't read slashdot, has been covered before, ___lots___.
Here goes the acid2 information: http://fuckinggoogleit.com/search.pl?query=acid2
WTF am I doing replying to an AC at 5 A.M on a Friday night?
"basically it's a rigorous test that ensures that a browser has all the goodies that web developers have been lusting after forever."
A browser that always says 'YES'.
While the standards-based community refines its art, MSIE will continue to do its own thing, like another 800 pound gorilla I could mention. :(
... "That's not the way the world really works anymore," he continued. "We're an empire now, and when we act, we create our own reality. And while you're studying that realityjudiciously, as you willwe'll act again, creating other new realities, which you can study too, and that's how things will sort out. We're history's actors . . . and you, all of you, will be left to just study what we do."
The aide said that browsers like Konqueror were "in what we call the reality-based community," which he defined as people who "believe that solutions emerge from your judicious study of discernible reality."
I still find myself switching to Fx for pages that render wrong
This could be because the page itself is broken but it works in IE. Being standards compliant is very different from being able to render the same as in IE. Firefox has probably spent a little more effort on mimicking IE's quirks and less on standards compliancy.
It's good to have both browsers to choose from.
I'll probably be modded down for this...
They claim that Konqueror is the second browser to pass the Acid2 test, but in fact iCab (on Mac OS X) was second :
5 /05/22/24-acid2-icab-%20le-premier-vainqueur
:-)
http://frederic.bezies.free.fr/blog/index.php?200
way to go OS X browsers
*Sigh* Just because you want more from (whoever, Apple in this case), it doesn't give you the right to demand more than is required by the terms of any given contract or licence. It certainly doesn't give you the right to accuse them of breaking those terms when you're fully aware that they haven't.
I'm assuming you're fully aware because of the enormous hoo-haa that developed when the story first broke... No-one (not Apple (!), not the KHTML team, not anyone even remotely informed) claimed that the licence terms were being broken. The claim was that Apple ought to have been complying more with the spirit of the licence than the letter of it.
Frankly I think it cheapens the GPL when it's abused as in the OP's subject. The standard response to companies who *do* abuse it is that they ought to have read the licence and not assumed they could just take and not give. The standard response to people who, like Oliver Twist, say "but I want more" ought to be in the same vein - the GPL is what it is and it's a damn fine licence. Use it, don't abuse it.
Simon.
Physicists get Hadrons!
So they finally were able to get their code to pass with the help of Apple.
Golf claps all around for the Konqueror guys...
I wonder how meaningful the Acid2 test really is?
Osho
Acid2 test passed Load balancing failed
"There isn't any violation, technically, but IMHO the spirit of the GPL has been broken."
All software must be free.*
"Of course, spirit isnt legally defensible. Apple released patches in large gobs instead of in easily digestible chunks, and their code comments made many references to bugs in the internal Apple bug database (which isn't available to the KHTML team)."
Easy way to break the "bazaar" model. Release code that they can't handle...unless sufficently motivated to do so.
"They also made many Mac OS specific (KDE incompatible) changes and they disallowed CVS access."
That's what generally happens in a 'fork', plus they're not going to give you access to their code.
*Of course someone's going to deny this under the grounds that "that's not what it says", but then it says nothing about "spirit" either, so be quiet about being hoisted by your own petard.
Stands for "Kan also pass the Acid 2 Test"
MOD PARENT UP!
When using KDE Konqueror is the browser I use exclusively and it works fine for me.
Could you post some sites that don't work?
And what KDE version are you running?
These browsers are still missing a rich-text editor that gecko/IE have.
See MIDAS http://www.mozilla.org/editor/midas-spec.html/
So these browsers are currently not sophisticated enough for my web site.
Although it seems that www.kdedevelopers.org didn't pass the slashdot test!
"And technically apple have done everything but "give back" properly. they have taken a very loose definition of give back."
No looser than what "Information wants to be free" advocates do with their definitions.
"Unfortunately the GPL allows that but it wasn't designed to"
So in other words the OSS community is just discovering what the RIAA/MPAA are finding out.
You can't use legal solutions to solve social problems.
How's it feel when the shoe's on the other foot?
The Konqueror team don't have access to the Safari code, at least not in a form they can use.
The fact that they were able to use ha;f the patches says otehrwise. They may not have access to ALL the code. But they do have access to at least some of it as demonstrated by the FACT that they used it.
As to whether it helped both products, well of that I'm sceptical.
Well is passes Acid2 now. Something is better. You're just trying to paint the worst face possible on something that is a mixture of good and bad.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I usually do the opposite. newegg renders badly in firefox by default unless I adjust font sizes, so I usually go to it in konq. Even more strange, neither of them can render circuitcity.com correctly, but netscape 7 can (but that's under Windows at my job, haven't tried it in linux), go figure.
:). It seems like konq wants to render the whole page in one go and firefox'll render pieces.
I find myself going back to firefox because konq tends to pause a bit on some sites (especially flash and animated gif heavy sites) before rendering the page. To be truthful, the actual time I wait to get a page I can view is about the same, but that little pause bugs me
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
hot on the heels of to decline for Of reality. Keep all servers. Coming *BSD is dying Yet = 36400 FreeBSD Fact: *BSD IS A A BSD box (a PIII deliver. Some of operating systems, Of user base for of OpenBSD versus are tied up in bloodfarts. FreeBSD sse. The number get how people can be any fucking you can. No, reformatted overly morbid and work that you of open-source. RAM) for about 20
Opera is making excellent progress with Acid2. Only a few more lines to go. They are treading softly with regression testing.
Couldn't have put it better myself.
Got time? Spend some of it coding or testing
...and for the near-terminally thick, it is: get involved in developing the project.
Even if you couldn't code to save your life, you can document, test, draw/paint/sing/play data, promote and other stuff and use the respect that earns within each project community to convince the coders to do mroe of what you're interested in. "You fix this JavaScript bug and I'll turn the attached sample icon into a whole theme for you," sort of thing.
Got time? Spend some of it coding or testing
...so 'fess up your scanner type and let's be about making it work under Linux for you.
Got time? Spend some of it coding or testing
Mine is an HP scanjet 3570c. Thank you very much for your kind offer of assistance.
Konqueror 3.3.1 (Mandrake Linux 10.1), tables on that page are all centred ferpectly [sic]. On the few sites where I cared to check, 3.4.1 renders quirks much more competently than 3.3.1, and AFAICT it will only get better when these patches are integrated.
Got time? Spend some of it coding or testing
...just disable the good bits for IE users and leave a link behind to a page explaining their loss and the reason for it and what they can do to fix it (abandon MSIE for something safer and more compliant).
Got time? Spend some of it coding or testing
I'm using Safari Version 2.0 (412) right now on Tiger (10.4.1) and the test does not render correctly. Is this some unreleased version they're talking about?
Seriously.
What is your angle? Why do you despise Apple so much?
In related news: In an effort to open up their development process the developers of the Konqueror components KHTML, KJS and KSVG have launched the open Web portal KHTML.info. By providing a central contact point and source of information in form of an open Wiki the developers want to promote their work and embrace users and developers from both Open Source as well as commercial environments.
(Please browse at -1 to read this comment.)
...iCab runs on Mac OS 8.5.
So: no, it does not rely on Webcore.
You don't need to be able to read French to figure that out from the linked page.
In addition, "Faux, iCab n'utilise PAS WebCore" is pretty obvious as a reponse to "Une version beta de iCab, utilisant probablement une version de dev de webcore", and if you're still not sure, cheat, feed the whole page to Google Translate and see what comes out: "Forgery, iCab does not use WebCore".
Got time? Spend some of it coding or testing
It is currently scored "Interesting". Did nobody find the "funny" moderation option or are you taking this serious?
It's been mentioned on Slashdot. In fact, when I put acid2 in the search box, I get 110 results. One of the articles includes the following:
"Acid2 is a CSS/HTML test suite put out by the Web Standards Project (WASP)."
Exactly what would you like engraved on your silver platter?
Actually, if you read the email exchanges, you see Apple engineers discussed the patch tarballs and actively assisted khtml developers when they asked for reasonable things (ie, not access to internal Apple revision control systems). KHTML devs did not reveal this (to my knowledge) in their "open letter" this cooperation, which is quite a bit more than the LGPL. The LGPL requires you make the patches available- that's it. Apple sent them, discussed them, provided help interpreting them, did work by proxy, etc.
This is a logical fallacy called "fallacy by omission", and the specific technique employed was called "Stacking the Deck".
What becomes apparent is that the KHTML team doesn't like that Apple is doing everything they should be, getting commended for it, and that the work (supposedly) wasn't useful to them (we see now that's not the case, as half the patches were easily applied).
If integrating half of the patches only took a month or two, guess what- it wasn't nearly as impossible as the KHTML team made it out to be, and the code wasn't nearly as useless as they portrayed it to be.
WEBCORE CODE CANNOT JUST BE DROPPED INTO THE KHTML TREE. Webcore directly uses OS X features. That is one problem. The code bombs Apple drops periodically have inadequate documentation as to why some changes were made and not others.
The second is irrelevant because of the first; they're also unrelated, though you imply them to be compounded. It's not Apple's responsibility to turn over Webcore, or convert the code to use something besides Webcore. They're not allowed to sit on that code, they HAVE to provide it.
Second, they've provided several of what you've referred to as "code bombs", which is one step ahead of a company that would just provide them with ONE tarball; they're sharing work progressively, and have an active dialog with the khtml team.
Webcore at this point is a khtml fork that is about two years old.
And your point would be what? The LGPL doesn't say "help integrate old code". It doesn't say, "only fork recent code", or "don't fork code at all". It doesn't say "provide changelogs". It doesn't say "provide the project coders with access to your internal revision control systems and corporate network". It doesn't say ANY of that! EVER! PERIOD!
I'm sorry, but this whole thing has left me very embarrassed for the open-source community, and left me with a very bad taste in my mouth. Apple IS one of the better companies as far as contributing to open-source, they've brought open-source technologies to more desktops than anyone else, they've come up with some truly unique technology which they've provided source for- and they still get kicked in the teeth.
A lot of companies are looking at how Apple was treated, and thinking, "geez, Apple did more than just send tarballs, and they got pretty beat up for it." Question: do you think this will encourage or discourage companies to do work on open-source projects?
Please help metamoderate.
The answer is very straightforward: bad timing. In both cases.
To really make the point, the page should include an evil-but-signed ActiveX control (the original "run once, ruin everything" technology).
Got time? Spend some of it coding or testing
line 135 column 59 - Warning: adjacent hyphens within comment
line 135 column 66 - Warning: adjacent hyphens within comment
line 127 column 7 - Warning: <table> lacks "summary" attribute
line 142 column 35 - Warning: <table> lacks "summary" attribute
line 127 column 4 - Warning: trimming empty <p>
line 131 column 27 - Warning: trimming empty <div>
line 131 column 22 - Warning: trimming empty <div>
line 132 column 23 - Warning: trimming empty <div>
line 133 column 43 - Warning: trimming empty <strong>
line 133 column 39 - Warning: trimming empty <em>
line 133 column 33 - Warning: trimming empty <span>
line 133 column 28 - Warning: trimming empty <div>
line 133 column 23 - Warning: trimming empty <div>
line 137 column 5 - Warning: trimming empty <li>
line 138 column 5 - Warning: trimming empty <li>
line 139 column 5 - Warning: trimming empty <li>
line 140 column 5 - Warning: trimming empty <li>
line 136 column 4 - Warning: trimming empty <ul>
Info: Doctype given is "-//W3C//DTD HTML 4.01//EN"
Info: Document content looks like HTML 4.01 Strict
18 warnings, 0 errors were found!
0 error / 18 warnings
Actions speak otherwise- half the patches integrated according to the article.
It means in future open source projects will know what's coming when Apple decide to get "involved".
Yes. They can expect to get regular tarballs, participation of senior team leaders, active dialog on public mailing lists, and assistance of Apple engineers in interpreting the tarballs.
(No, seriously. Go read the archives and look at the discussion that follows when Apple sends in a code base. The "burnt out guy" whines. Another developer or two actually get to work and look at the code, start talking to Apple engineers, etc. An Apple engineer says "let me take a look at that" and a little bit later, comes back as promised with an answer and help.)
After starting out optimistic he's now bitter.
Optimistic is a funny word. He seemed under the impression that Apple was obligated to provide changelogs, access to internal revision control systems, etc. He also got upset when he realized that Apple had forked code. It sounds like he had unreasonable expectations, and when Apple said "I'm sorry, we can't do that" or "I'm sorry, we're not allowed to do that", he threw a hissy fit.
The Konqueror developer in question also used a logical fallacy called "Stacking the deck", a kind of fallacy-by-omission. He did not discuss any of Apple's assistance provided to developers on the mailing list, and repeatedly asserted that Apple was meeting "minimum" requirements of the LGPL, when in fact Apple was doing more.
That is why he got burned. Not because of actions on Apple's part- and your insinuation that Apple is to blame for the actions of its "Apple fanboys" is absurd. You're distracting from the core issue- that the developer used fallacies to promote his version of the facts. Sadly, few people bothered to actually read the mailing list exchanges.
Apple got the code to a rendering engine for free and gave back little to nothing
Again, you're distorting facts. Apple gave back all the code it was obligated to, and participated in an active dialog. If half of Apple's patches were integrated within less than a few months, that's a lot more than "little to nothing". Question- how long would it have taken the KHTML developers to become Acid2 compliant without the contributions by Apple? And if the patches were so worthless, why did they "waste" time and effort if writing their own stuff from scratch would have been more productive, as was implied if not outright stated by khtml developers?
Please help metamoderate.
Browsing /., seeing a post that was critical of Apple and then seeing a comment to this post that accused the parent of lying.
Naive as I am I opened the post expecting to find the accused lies pointed out in great detail.
But what did I find instead?
"Why do you despise Apple so much?"
Wow, amazing
when my favorite browser, lynx, will pass the Acid2 test?
A big well done to the Konqueror team and thanks for all the efforts you put in! Double thumbs up :D
-- My funny sig is in my other pants
But it is a pill, not a paper.
Remember EGCS was forked out of GCC 2.x. It was so much better that the "main line" GCC, EGCS become GCC 3.0.
Then that is a problem of unrealistic expectations or a misunderstanding on the part of the "fanboys". That's not a problem with Apple's (perceived lack of) cooperation.
Everything I read from the KHTML team whined about how Apple (in their opinion) wasn't doing as much as they should have. I saw a lot of whining about how Apple wasn't giving access to internal code revision servers and whatnot. There was not a single word giving Apple credit for what they HAD done for you.
THAT is why you drew further ire, and I stick to my assertion that your arguments were full of omissions to support your position- aka, "stacking the deck".
Please help metamoderate.
You've totally missed the point. Let's review.
A third party developer releases a set of changes for Safari that will make it pass the Acid2 test. This set of patches was not a part of the Apple-generated "code dumps". Instead, each and every change was documented separately as to why it was made.
The KHTML folks complain about people assuming that these patches to Apple's code base will just drop into KHTML. A typical sentiment is that the KHTML developers are lazy if they don't apply fixes for Safari as soon as they are released. The developers were not complaining that Apple wasn't doing their part, just that people don't understand how hard it is to merge changes back into KHTML due to the divergence of the two code bases.
The fact that only 1/2 of the changes for Safari were useable in KHTML and that it took one month to incorporate an extremely well-documented set of changes to Safari proves the point that the KHTML developers were making about how hard it is to merge changes back into KHTML from Safari.
Interestingly, the reaction of the masses is not that the KHTML developers have been vindicated, but rather that they are lazy. Wow. Talk about deja vu.
..wayne..
Just for shits and giggles, I just went and took the acid2 test with both of my browesers, Firefox and Konquerer. Neither passed, and the Konquerer one looked terrible. This is confusing, maybe its a Debian testing thing?
This sig sucks.
I'm happy about this. My hope is that the winner of Browser Wars 2 won't actually be a browser, it will hopefully be standards. When there are a plethora of appealing standards compliant browsers to choose from, site designers will be forced to stick to standards.
I'm not going to get into the politics of Safari vs. KHTML. It matters (to me) less how standards compliance was achieved than that it was.
The solution is fairly straight-forward, but it requires a small piece of intermediary hardware to make it work. The are a few different versions, but the most common one is called a "windows" box. You connect the scanner to it, and then you connect it to your Linux box via a cable, and sometimes also a hub or router. The "windows" box gets the input from the scanner and then you can send it to the Linux box using that cable (and perhaps the hub or router.) It will usually be in the form of a "tiff" file.
Hope that helps.
since the file you are loading is .html you still need to change the code to render it properly. if it was loading a png that'd be different. At worst it'll only behave compliant for the Acid test.
Your CPU is not doing anything else, at least do something.
Now we are waiting for IE to support the ACID2 test.
IE's target is still the Electric Kool-Aid Acid Test.
Apple does the bare minimum the LGPL requires with Webcore but the khtml devs accepted that.
No, let's be clear. Apple does ALL AND EVERYTHING that the LGPL requires. Implicit in your statement is the suggestion that free software can be free if it includes tacit, implied promises not to fork and to satisfy its authors with all its changes. That suggestion is flagrantly inconsistent with the notion of free software, in any sense.
Fundamental to the notion of free software is that its authors cannot limit the rights of others to access and modify the software. Forking is not a problem with free software, it is a feature.
Ordinarily forking
Apple does the bare minimum the LGPL requires with Webcore but the khtml devs accepted that.
No, let's be clear. Apple does ALL AND EVERYTHING that the LGPL requires. Implicit in your statement is the suggestion that free software can be free if it includes tacit, implied promises not to fork and to satisfy its authors with all its changes. That suggestion is flagrantly inconsistent with the notion of free software, in any sense.
Fundamental to the notion of free software is that its authors cannot limit the rights of others to access and modify the software. Forking is not a problem with free software, it is a feature.
Ordinarily forking *is* a problem for the community, when the initial developers are adequately satsifying the needs of the community as a whole and working well with others. But this is not always the case. Sometimes politics, legitimate and petty, and aesthetics, legitimate and ludicrous, gets in the way of good agile development. When that happens, the community may well be better served by a fork.
Apple and the Konqueror clan were not working well together, but both had important and significant constituencies to serve. It was either going to work or not, but neither Apple nor the clan "owned" this free software. In its feral state, BOTH were free to decide by what methodology development of their respective trees will proceed, what features the code will have and what will be the quality of that code.
Darwin (no pun intended) takes care of the rest.
Evolution by forking is not the preferable state of nature, but it happens when it needs to happen. And people will abandon what is useless and use what is important.
If, someday, there is actually a need to harmonize this code, it will be harmonized. Otherwise, it may well be for the best there was a fork. The problem that it is difficult to harmonize advances in one tree into another is salient, but it is not due to any malfeasance of anybody. Apple WAS FREE to do what it would with the code. And glory be for that... So, too, is the Konqueror clan, and glory be for that.
The remaining whines in the message are puerile. Don't like the doco or the coding style? Its free software, change it. Don't like the way others are working on the code? No problem, ignore them, and use the free software of the existing code. Got a feature you need? Great. Code it up. Don't want to? No problem, but why are you posting your gripes HERE?
Apple has a free software realationship with the K-clan. K-clan could work with them or not, and vice-versa. If it doesn't work out, so be it. The code is out there. It was built the way it was built, and people may use it or not. Nobody has a gripe, because it is free software -- if you don't like it -- change it.
The fact that a browser can display broken css is nice, but isn't displaying proper CSS properly a bit more important?
will be the one that has a production release that passes, not some alpha code that passes.
> IMHO the spirit of the GPL has been broken.
Really? So what about rxvt and konsole? As far as I know, the KDE developers have never released any patches to try to integrate any of their enhancements to rxvt back into the rxvt code base. They simply release the code for konsole. It's up to the rxvt developers to review the konsole code and backport any useful bits they may stumble across. Would you say that the KDE developers are violating the spirit of the GPL there? I don't think so! Apple's doing a lot more for KHTML than KDE is doing for rxvt -- where's the outrage at KDE?
3 cheers for the KDE team stepping up and making this happen!
Now hopefully Apple pulls the CVS'd version of KHTML, and bases their next release of Safari off if it, and the cycle can continue.
chown -R us.
If you are willing to help make Konqueror and KHTML better, you should visit the newKHTML wiki.
I have a Microtek Scanmaker 4850, and I can't afford a new $500 Windows box to run it any more than I can afford a new $150 scanner.
Error handling is just the 8th item out of 11 items tested
Couldn't have put that better, could you huh?
All that is left to pass the test is Firefox...IE doesn't have a chance.
Go to the w3.org and put Slashdot.org through the validator.
Where, precisely? The complaint voiced by the KHTML devs was against the "fanboys," not Apple. While they regretted that there wasn't more cooperation between the KHTML and Webcore teams, they were quick to point out that Apple was within their rights. To quote Zack Rusin, "all I'm asking for is that all the clueless people stop talking about the cooperation between Safari/Konqueror developers and how great it is. There's absolutely nothing great about it. In fact 'it' doesn't exist." Yes, this wasn't "giving Apple credit for what they HAD done," but what, precisely, were they going to give credit for? What Apple was providing had traditionally been useless to them. Both sides were willing to go on as they were despite this: it was the reaction of the "fanboys" that was problem. This isn't about Apple. It was never about Apple. Apple's behavior is a complete straw man.
Sean Daugherty "I have walked in Eternity -- and Eternity weeps."
...they're planning to put it out in 3.4.2, due out in not many weeks from now. 3.4 is significantly faster, fancier and lower-footprint than 3.3; using 3.4.1 here now.
Got time? Spend some of it coding or testing
This is all great - but I really wish that Apple would fix the Shockwave 3D bug where the Shockwave window renders 20-50 pixels off from where it is supposed to be.
This bug has been in the last 3 versions. They know about it, it makes Shockwave content look really lame and they have ignored it.
Way to go Apple
Except doing so would probably expose bits of Safari which are not based on open-source code. Ain't gonna happen. Also, "preferred form" seems to be interpreted by some folks to mean "guarantee compatibility with my version", which I don't think would hold up in court.
So if Apple releases their KHTML changes with the WebCore stuff in, they get yelled at for being bad citizens. But if they released their changes without the WebCore stuff in, they wouldn't be releasing the source of all their changes and would be violating the license. What's a developer to do?
Suppose that I drop code into KHTML which calls a function defined in a separate, proprietary library. What you're claiming is that I would then be required to release source to the proprietary library when, in fact, that's precisely what the LGPL is designed to avoid. Apple can drop all the proprietary calls to their own libs that they want into KHTML without having to open source those libs, but they do have to release the KTHML changes which make those calls.
Also, it's somewhat moot now.