| Specific features |
References |
|---|
- X3D Support
- Support to visualize content X3D, it would allow to work in improving the interactivida one of the hand of a great navigator
- (I request excuses by the text I do not speak English and to use the translator of google :) )
- Please somebody that complements the importance of including X3D in firefox.
|
|
- WPF/XBAP Support
- I know that this is going to be a hot-button topic, but WPF and XBAP is coming whether we like it or not. It would be sad if cool WPF/XBAP applications were only available on IE.
|
Introducing Windows Presentation Foundation
|
- ACID 2 test
- Make sure Firefox passes it
|
Bug 289480
|
- Full SVG 1.1 support
- Add full support (not a non-standard subset of it) of SVG 1.1 or TinySVG 1.2
|
W3C SVG1.1
|
- Content-editable
- Add support for content-editable
|
tinysvg w3c
|
- CSS
- Make "display: inline-block" work correctly
- Support for "content" on all elements, not just on the :before and :after (like Opera)
- Implementation of the value "none" for the property "content". (w3c-content)
- Complete support for Multiple background images (like Safari)
- Basic support for "border-image".
- Support "text-shadow" (like Konqueror/Safari does)
- Support printing-related properties such as page-break-before and page-break-after
- Implement CSS3 column-rule-*
|
Bug 9458 (inline-block)
multiple-background-images
border-image
Bug 24000 (page-break)
Bug 10713 (text-shadow)
Bug 271586 (CSS3 column-rule-*)
|
- XForms
- XForms supported and built-in.
|
Bug 326372
|
- XHTML 2.0
- Add support for current XHTML 2.0 draft
|
Bug 161463,
XHTML2 Working Draft
|
- new DNS like system
- Having a mapping between domain names (evt. as a RegEx) and IP.
The idea is to be able to edit site that don't have a DNS entry, when we develop a new version that is not on the "real" site.
It's like to change this file: C:\WINDOWS\system32\drivers\etc\hosts but included in firefox.
|
n/a
|
- XHTML ruby annotation
- Ruby annotation has been included in XHTML spec since 2001, and there has been a great extension to implement it. Now, let's make it in Fx 3.
|
Bug 33339 - XHTML ruby support,
XUL Apps > XHTML Ruby Support
|
- shy
- Add full support for soft hypens.
|
Bug 9101
|
- IE Compatibility
- Answer to below suggestion: Integrate IE tab into firefox by default.
- Add fallback mode to support non-standards based rendering when "IE only" features are present in a web page so that the page will render correctly. Allow feature to be turned on and off. Could be made into a plug-in instead of putting feature directly into Firefox. This feature would allow more people to convert to Firefox and leave IE behind forever.
- Agreed with the above statement. I have companies that insist I use MSIE, even if I'm in linux. I believe Opera has the feature whereby it uses the MSIE engine, but I haven't tested it on these sites. This needs to fix the problem of a) a site refusing to even load, if your using anything but MSIE, b) allowing uploads of files even with FF (over IE)
- Support for embedded managed code objects (ie .NET Windows Forms or platform independant MONO assemblies)
|
n/a
|
- XSLT 2.0
- W3C Candidate Recommendation 8 June 2006
|
XSLT Candidate Recommendation
|
- XSL-FO 1.0
- W3C Recommendation 15 October 2001
|
XSL-FO Recommendation
|
- Full HTML 4.01, and CSS 2.1 compatibility.
- Increase the standard bar in HTML, and CSS standard.
- Firefox should work hand-in-hand with the W3, to be 100% compabiable with the current CSS/HTML/XHTML standards, so we web site writers can write our sites with FF in mind, and let IE, and others play catch-up. Also, FF should be updated quickly in order to be current with the next versions of such. We've wanted CSS, and such for years, and now we get it, it's the browsers that stop us from accually using it fully. There is no really good reason why at least FF shouldn't be 100% compatible (IE has an exchuse but I'm not going to bash companies here :)
- What's wrong with aiming for full CSS3 support? This is FF 3.0 we're talking about. Surely CSS 2.1 support is a given, and 3.0 is achievable in the timescale we're talking about.
|
Browser standard comparison
|
- iCab-Smiley analogue
- This nice feature will promote standard-compliancy of the web.
|
iCab wikipedia page
|
- MHT / MHTML Support
- Saveing / Reading of MIME Encapsulation of Aggregate Documents, such as HTML
| RFC 2557
BUG 18764
BUG 40873 |
- SMIL support
|
REC SMIL 2.0
|
- XInclude Support
- Including XML files or fragments.
|
Bug 201754
Bug 232378
XInclude 1.0
|
- align=char support
- Allow text to be aligned by a character or string in a table cell.
- Example - centre numbers around a decimal point, as in a spreadsheet.
- Part of the overall standards compatibility, but I think it deserves highlighting.
- Bug raised in 1999!
|
Bug 2212
Test Case
Another Test Case
|
| Library Compatibility |
|---|
|
KDE compatibility
- A Qt based firefox to remove dependencies on GTK.
|
n/a
|
| General tasks |
|---|
- Improve overall standards support
|
n/a
|
- Improve interoperability of XML languages
- HTML and MathML in SVG foreignObject elements
- SMIL to animate web pages
- interface for plugins to handle mixed XML languages. Final goal: FF + plugins should be able to handle a SMIL + XHTML + MusicML + SVG + ... document
|
VML+SMIL+XSLT Demo in IE
|