-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurestype-enhancementA request for a change that isn't a bugA request for a change that isn't a bugweb-librariesIssues impacting dart:html, etc., librariesIssues impacting dart:html, etc., libraries
Milestone
Description
This issue was originally filed by @seaneagan
The dart:html library is huge. This leads to some issues:
* makes the documentation extremely difficult to navigate
- importing dart:html really clutters your namespace
- prefixes must be used on top-level names in dart:html to avoid
conflicts with other parts of the library - if it is not split up now, it will only get bigger over time
It should be split up into smaller libraries. The challenge of course
is where to draw the boundaries for the smaller libraries. Here are
some approximate subsets which should probably be their own library:
SVG* (154 names!)
Audio* (21 names)
CSS* (18 names)
IDB* (18 names)
WebGL* (17 names)
Worker (13 names)
Speech* (12 names)
typed arrays (11 names)
see https://developer.mozilla.org/en/JavaScript_typed_arrays
Canvas* (5 names)
geometry
see issue #3107
Metadata
Metadata
Assignees
Labels
P1A high priority bug; for example, a single project is unusable or has many test failuresA high priority bug; for example, a single project is unusable or has many test failurestype-enhancementA request for a change that isn't a bugA request for a change that isn't a bugweb-librariesIssues impacting dart:html, etc., librariesIssues impacting dart:html, etc., libraries