|
|
Avoiding it altogether...
Of course, a much better way to avoid this bug altogether is to use OmniWeb. Although it's not necessarily as good of a browser of IE (marginally), it's definitely a better program: it is more stable, takes less memory, and meshes with OS X a bit better. It doesn't maximize below the Dock, uses OS X widgets, and (I think) it follows Apple's interface guidelines.
Avoiding it altogether...
Of course, a much better way to avoid this bug altogether is to use OmniWeb. Although
it's not necessarily as good of a browser of IE (marginally), it's definitely a better program I'll agree the program is good, but the rendering engine leaves much to be desired. It has no support for CSS1, CSSP, (both in wide use today), CSS2, XML, or XSLT. It has the same problem as iCab: good end user features, but only very basic rendering support . I think both OmniWeb and iCab would be good to consider adopting Gecko, and focus on development of end user features. I'm not a huge Mozilla fan, but the fact is that it's a long, difficult road to do CSS support right. - Scott |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.26 seconds |
|