| Specific features |
References |
|---|
- Make spellchecker standard-friendly
Firefox is known for its compliance to standards - then suddenly it introduces the "spellcheck" attribute. How are we any better, then, than Microsoft and all its superfluous DOM extensions? Please, put the spellcheck attribute in a namespace, get it approved by the W3C, or drop it.
|
|
- Report site health at runtime
Do not wait till pages are terminally broken before failing users and developpers. Provide unobstrusive run-time feedback on the errors encountered so pages can be proactively fixed
- The HTML validator extension shows how such a feedback could be provided without overwhelming the user. Its main value is errors/warnings are detected when they occur, not when someone thinks about looking for them.
- If you wait till people take the time to open the debugger/console and/or run the various offline validators you've already lost.
- You can't blame non-technical people from setting up broken websites or webapps if the PHBs have no easy way to check the contractors actually delivered clean code.
- Showing a Faulty-Icon in the Statusbar when in Quirks-Mode might be a way that is easily accessible to developers and not disturbing the common user.
|
|
- PDF internal Support
|
|
- iCalendar Support
- Support to visualize iCalendar content
|
hCalendar Microformat
|
- 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.
- If internet browser will be view X3D/VRML by default (without plugin) they make revolution in the network - because it's good stimulus for developers (view that you do) - all will be make 3D models and worlds. It is simple and interesting - give they view instrument!
|
|
- ACID 2 test
- Do make sure Firefox passes it.
- Keep eye out for ACID 3 test (no date exists yet as far as I am aware, but they have stated their intent to do such a test). If it is released before 1.9 needs to be ultra-stable, try and get it passed beforehand (mostly for PR purposes really).
|
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
- Make SVG "scalable" : When viewing a SVG File, it should be possible to zoom in and out
|
W3C SVG1.1
|
- Graph-support
- Add support for Graph-Formats including GraphML and GML/XGMML (ie. by converting to SVG)
|
|
- Content-editable
- Add support for content-editable
|
tinysvg w3c
|
- CSS
- 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)
- Make "display: inline-block" work correctly
- Make "display: run-in" work (bug raised in 1998!)
- Implement support for multiple backgrounds following CSS3 W3C Standards (like WebKit/Safari)
- Basic support for "border-image".
- Support "box-shadow" (w3c-box-shadow)
- Support "text-shadow" (like Konqueror/Safari does)
- Support printing-related properties such as page-break-before and page-break-after
- Implement "-moz-crop" property (w3c-crop)
- Implement CSS3 column-rule-*
- Implement CSS3 column-break-* (at least column-break-inside:avoid is required to be able to prevent a zone from beeing "cut in the middle" on resizing).
- Implement CSS3 border-radius that it's similar to -moz-border-radius.
- Implement font-stretch property
- Implement embeded Font (@font-face to TTF, OTF or EOT ), will benefit also to SVG
- Implement
scrollbar-XXXX-color properties (allow web authors to control scrollbar colors), like in MSIE/WIE
|
|
- XForms
- XForms supported and built-in.
- Do also have a look at HTML 2.0 Forms
|
Bug 326372
W3C HTML 2.0 Forms Spec
|
- XHTML 2.0
- Add support for current XHTML 2.0 draft
|
Bug 161463,
XHTML2 Working Draft
|
- Java support
- Activate JavaXPCom on FF (already default on XULRunner 1.8.0.4+)
- Ease extensions creation using Java, ie "pluglet like"
|
JavaXPCOM |
- Javascript support
- Make the control and shift keys again available like in 1.5 because programmed keyboard hot links do not work anymore.
|
|
- XPointer support
|
|
- IPv6
- IPv6/IPv4 preference. When a site got both, an option should indicate which one is preffered.
|
Bug 213121 |
- 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)
- WPF/XBAP Support.
|
Introducing Windows Presentation Foundation
|
- Opera-like XHTML error processing
- When opening an XHTML document with a syntax error, Opera shows a source fragment with lines numbers and both the tag where the error's been found and the tag that is missing its closing part highlighted.
- There is also a "Reparse document as HTML" link.
- (very optional) There is also a link to the format specification.
|
Open in Browser extension
|
- 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
- We may also wish to support the MAFF format too.
| 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
- Provide I18Ned mozilla.com/getfirefox.com website (beeing english only is not user friendly, site should adapt to user's locale).
- Improve support for High DPI screens
- Use scalable graphics (eg. SVG) for FF UI icon and image. Make scalable graphics first class citizen in FF.
|
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
- To make this happen, a plugin should be able to subscribe to an XML type (e.g MathML, CML, SVG, SMIL) and Firefox would have to pass control to this plug-in when such XML elements are parsed. On the other hand, one cannot rely on the plug-in to give control back to firefox, when encountering other XML standards. So either Firefox itself has to care about every part, or there has to be a close cooperation with plug-in developers to ensure this. All in all the possible nesting of XML standards using namespaces should be supported as far as possible.
|
VML+SMIL+XSLT Demo in IE
|
|
Make the property in CSS of direction (ltr) work properly (is it just me or isn't it working?
|
- Support the visualization of mails
Mails are one of the most common kind of documents around. Many times there is a need to publish them in web sites. To do this today, mails have to be converted to some document format that a browser can display, like, e.g. html. Removing this transformation would simplify considerably the publication of this type
of contents in web sites.
|
|