• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

IE7 - Firefox Url Handling Bug Caused By Windows

HellasVagabond

New Member
Joined
Jan 19, 2007
Messages
3,376 (0.50/day)
Location
Athens , GREECE
System Name SECONDARY RIG / PRIMARY RIG / THIRD RIG
Processor i920@3.6GHz / i920@4GHz / AMD Phenom II 955
Motherboard Gigabyte EX58-UD4P / Gigabyte EX58-UD7 / ASRock 890GX3
Cooling CoolIT Domino ALC / Thermalright Silver Arrow / Thermalright VenomousX
Memory 12GB DDR3 @ 1800MHZ / 6GB DDR3 @ 2250MHZ / 4GB DDR3 @ 1600MHZ
Video Card(s) XFX ATI RADEON 5970 / GAINWARD NVIDIA GTX 580 / 2xGEFORCE GTX295
Storage 1550GB / 6TB SAS - SSD / 160GB SSD
Display(s) NEC 26WUXi2 / NEC 3090WQXi / SONY 55A2000 (1080P 55inch)
Case COOLER MASTER HAF 932 / COOLER MASTER ATCS 840 / ANTEC DARKFLEET DF85
Audio Device(s) Soundblaster X-Fi Xtreme Music / SoundBlaster X-Fi Fatal1ty Pro / Realtek Onboard
Power Supply CWT 1200W / Enermax Revolution 85+ 1250W / Ikonik Vulcan 1200W
Software Windows 7 x64 / Windows 7 x64 / Windows 7 x64
An exploitable bug in Mozilla Firefox discovered earlier this month was first believed to have been caused by Internet Explorer 7 but soon after that Mozilla was forced to admit that it was Firefox that could trigger the bug as well. Today however that bug has apparently been traced back to a Windows API function. However Mozilla seems to have fixed the bug in their latest Firefox 2.0.0.6 version.

View at TechPowerUp Main Site
 
Last edited by a moderator:
Well this clears up any disagreements from the initial news post comments about this. People were ready to slam Mozilla for being "quick to judge". Perhaps they were, but this shows it wasn't FF's fault.
 
I think its just cool how the bug has been in IE all this time, and then within days of the same exploit being found in Mozilla, that it was fixed straight away :p.
 
I think it is easier to fix something when you have 1 product than when you have 100 so in a way i don't really blame MS. Besides i am sure they will fix it fast now that it is known that it's Windows fault.
 
I think it is easier to fix something when you have 1 product than when you have 100 so in a way i don't really blame MS. Besides i am sure they will fix it fast now that it is known that it's Windows fault.

Well M$ does have dedicated teams per project, so IE has never had an excuse for bugs.
 
Actually most teams in Microsoft shift projects from time to time according to what project needs more help. However some people stay in every project.
 
Caused by a windows API function.. reeks of M$ discreetly trying to stop mozilla from working on at least their "new baby" Vista. Talking of Vista, I saw a laptop roundup in a mag, think it was PC Pro, only 2 laptops were still using XP, but they absolutely slammed and decimated the Vista based machines in all areas.
 
::grin Ketxxx::


good to know it wasnt FFs fault, but I still stand behind the comment that within 2 or so days, the problem was fixed with a WINDOWS API error for Firefox (perhaps ms is trying to keep FF off vista?)

And the thing with MS, they have dedicated teams, this should have been fixed with IE soon after it was discovered.
 
Back
Top