Full-text blog feedFavourite Firefox Bugs
While we're on the subject of Firefox bugs I thought I would post a list of my favourites. Well, calling them favourites is maybe a bit off, since I can't wait to see them nuked off the face of bugzilla:
- Bug 9101: Break lines at soft hyphens (­) and display hyphens if line broken.
- Bug 98971: Prettier image resizing & scaling (Bilinear, Bicubic, anything better than Nearest Neighbor).
The above two are what I would call the most important Gecko bugs right now. They both do their part for preventing truly scalable website design. For instance, if the latter one was fixed, website designers would be much more inclined to specify image sizes in em units and the images would resize beautifully with the rest of the content.
Then there are a few other bugs which also would be nice to have fixed. These are definately lower prioroty though, IMO:
- Bug 16380: Need anti-aliasing for -moz-border-radius style property.
- Bug 75077: Interlaced PNGs should be displayed with bicubic interpolation.
Then of course, there is the Acid 2 bug, which is being worked on as we speak - and may well be fixed for Firefox 2.0.
2 Comment(s):
At 8:08 PM,
xeen said…
I agree with all of the mentioned bugs. While is less important to the web like it currently is, I guess that image resizing is the most important one as it is used e.g. for displaying images only in Firefox (resize if pic> view size) and it is used more commonly.
However, if you want a resizeable page, with relative units and all that stuff is quite important though it would take much time to write a text ing all possibles things.
At least , better image resizing combined with the column layout would it make it WAY easier to read texts on high resolutions. The main problem is that you loose the line if its too long therefore most pages with longer text use only 50% or less of my screen, which defently sucks.
At 8:53 PM,
David Naylor said…
Yeah. Scalable designs are the future. I can't wait for these bugs to be fixed - at least the first two.
Post a Comment
<< Home