User:Ctalbert:Fx3:ContentHandling: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 6: Line 6:
|'''The Idea''' || Improve the parsing of microformats so that extension authors are free to innovate without having to worry about parsing the data.
|'''The Idea''' || Improve the parsing of microformats so that extension authors are free to innovate without having to worry about parsing the data.
|-
|-
|'''Wiki Pages''' || [[User:Mkaply:Fx-Docs:Microformats|Design]] | [[User:Mkaply:Fx-Docs:Microformats/Architecture|Architecture]] | [http://wiki.mozilla.org/Firefox/Feature_Brainstorming:Microformat_Handling Brainstorming]
|'''Wiki Pages''' || [[User:Mkaply:Fx-Docs:Microformats|Design]] | [[User:Mkaply:Fx-Docs:Microformats/Architecture|Architecture]] | [http://wiki.mozilla.org/Firefox/Feature_Brainstorming:Microformat_Handling Brainstorming] | [[Microformats/UE/ideas| UI Design]]
|-
|-
|'''References''' || [http://microformats.org/ Microformats.org]
|'''References''' || [http://microformats.org/ Microformats.org]
|-
|-
|'''Test Plan''' || TODO
|'''Test Plan''' || [[MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:Microformats|Test Plan]]
|-
|-
|'''Tests'''|| TODO
|'''Tests'''|| TODO
|}
|}
'''Bugs'''
'''Bugs'''
'''Other Information'''
* This is going to be almost an entirely back-end feature to enable extension authors to do more with microformats.  To that end we probably want a set of automated testcases that test the exposed APIs that this feature will expose and a set of microformat pages to use for testing against.
* Conversation with mkaply about getting a working version of this code:
<pre>
[3:48pm] ctalbert: Is that code in the downloadable version of Operator (0.7 from Add-ons)
[3:49pm] mkaply: ctalbert. No it's in SVn.
[3:49pm] mkaply: http://svn.mozilla.org/labs/operator/chrome/operator/content/Microformats/
[3:49pm] mkaply: This is the Fierfox code but removing xFolk and tag
[3:50pm] sheppy left the chat room. (Quit: ¡Hasta la vista!)
[3:50pm] mkaply: You can put Microformats.js in the components directory for now.
[3:50pm] mkaply: Then do
[3:50pm] mkaply: Components.utils.import("rel:Microformats.js"); at the top of a chrome JS file
</pre>
* This will enable us to begin work on an automated test framework
* [http://microformats.org/wiki/hcalendar-examples-in-wild List of Sites] that employ hcalendar types of microformats (also useful for web protocol application testing).


= Web Content Handling =
= Web Content Handling =
Line 25: Line 42:
|'''References''' || [http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers Web Apps Spec 1.0]
|'''References''' || [http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers Web Apps Spec 1.0]
|-
|-
|'''Test Plan''' || TODO
|'''Test Plan''' || [http://wiki.mozilla.org/MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:Content_Handling-WebProtocol_and_Application Content Handling Test Plan]
|-
|-
|'''Tests''' || TODO
|'''Tests''' || [http://wiki.mozilla.org/MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:Content_Handling-WebProtocol_and_Application#References Tests in Litmus]
|}
|}
'''Bugs -- Just some high level ones, refer to dependency tree'''
'''Bugs -- Just some high level ones, refer to dependency tree'''

Latest revision as of 23:46, 6 July 2007

This page is a (hopefully) useful clearinghouse to find information on three of the high-profile content handling changes underway in the Gran Paradiso (Firefox 3) effort.

Microformats

The Idea Improve the parsing of microformats so that extension authors are free to innovate without having to worry about parsing the data.
Wiki Pages Design | Architecture | Brainstorming | UI Design
References Microformats.org
Test Plan Test Plan
Tests TODO

Bugs

Other Information

  • This is going to be almost an entirely back-end feature to enable extension authors to do more with microformats. To that end we probably want a set of automated testcases that test the exposed APIs that this feature will expose and a set of microformat pages to use for testing against.
  • Conversation with mkaply about getting a working version of this code:
[3:48pm] ctalbert: Is that code in the downloadable version of Operator (0.7 from Add-ons)
[3:49pm] mkaply: ctalbert. No it's in SVn.
[3:49pm] mkaply: http://svn.mozilla.org/labs/operator/chrome/operator/content/Microformats/
[3:49pm] mkaply: This is the Fierfox code but removing xFolk and tag
[3:50pm] sheppy left the chat room. (Quit: ¡Hasta la vista!)
[3:50pm] mkaply: You can put Microformats.js in the components directory for now.
[3:50pm] mkaply: Then do
[3:50pm] mkaply: Components.utils.import("rel:Microformats.js"); at the top of a chrome JS file
  • This will enable us to begin work on an automated test framework
  • List of Sites that employ hcalendar types of microformats (also useful for web protocol application testing).

Web Content Handling

The Idea Allow Firefox to hand-off content to web-based services in addition to local applications.
Wiki Pages Web Service Mime Handling | Content Type Processing | Firefox Reqs
References Web Apps Spec 1.0
Test Plan Content Handling Test Plan
Tests Tests in Litmus

Bugs -- Just some high level ones, refer to dependency tree

  • Testcases added/updated (testcase link/id for Litmus/Automation Tests)

Download Manager

The Idea Shave off some of the rough edges in the download manager. Allow for ability to resume downloads from one Fx session to the next
Wiki Pages Download Mgr Spec | Resume Download Design | More download resuming
References
Test Plan Test Plan
Tests TODO

Bugs -- Just some high level ones, refer to dependency tree

  • Testcases added/updated (testcase link/id for Litmus/Automation Tests)
Retrieved from "https://wiki.allizom.org/index.php?title=User:Ctalbert:Fx3:ContentHandling&oldid=61370"