1
edit
Talk:Firefox:2.0 Product Planning:Draft Plan: Difference between revisions
Jump to navigation
Jump to search
Talk:Firefox:2.0 Product Planning:Draft Plan (view source)
Revision as of 16:36, 21 December 2005
, 21 December 2005no edit summary
No edit summary |
|||
| Line 47: | Line 47: | ||
* Veeven: Anti-aliasing of fonts makes web pages look better. I think it may not be possible for Firefox 2.0. But, it is much needed to improve the visual look of any web page. [http://www.w3.org/Amaya/ Amaya] does it already. | * Veeven: Anti-aliasing of fonts makes web pages look better. I think it may not be possible for Firefox 2.0. But, it is much needed to improve the visual look of any web page. [http://www.w3.org/Amaya/ Amaya] does it already. | ||
= Support for JPEG2000 = | |||
* momendo: JPEG2K has been released as a standard and there has been very little movement in the browser world to support it. We have a chicken/egg scenario where browsers don't really need to support it unless there is a strong need. JPEG has become a very popular format for photos. Digital cameras don't support J2K but if it's supported in the browser, the case becomes really strong to support it. There is a bug filed for it [https://bugzilla.mozilla.org/show_bug.cgi?id=36351 here.] J2K can really improve image quality and save bandwidth. PNG overlaps some of the features of J2K. But I would argue J2K has better PSNR and can be lossy if needed. Once it's in trunk, it can be used in tags like Canvas with alpha channel. | |||