This reminds me of the Pentium floating point bug.
Intel didn’t want to replace the processor because the average joe would only run across it under certain conditions.
Rather than say thanks. Intel fought replacing it until the low roar became a din and they finally decided to replace it “upon request”.
Seems Apple could have just said, hey thanx! Fixed it and be on there merry way....and hire the guy who set up the test as a QA guru.
But there are still too many Mac v. PC fire breathers and it produces crap articles like these - blame the guys who find and report the bugs.
Apple HAS said thanks and is fixing this minor fur ball. It is not a major problem that effects users of the MacBook Pro who use it as it is MEANT to be used. 99.9% of users never turn on the Developer Menu in Safari and will never find the commands to turn them off.
And the fact is that CR did not find it, Apple did in trying to figure out what CR did to get such crappy results! Apple thanked them for discovering the crappy results under very unusual circumstances, but CR had not a clue about why it was doing it.