If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[mortar] Research x-tags for future templates

RESOLVED FIXED

Status

Developer Ecosystem
Dev Kit
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jlongster, Assigned: jlongster)

Tracking

Details

(Whiteboard: u=dev c=mortar p=2 s=2013.9)

(Assignee)

Description

4 years ago
Need to establish a process for how we are going to use x-tags in the next version of the templates. I think we should look at Polymer to see how they are doing it, just for some outside ideas. Most likely we'll just bundle a bunch of tags into a single js file, and we need to figure out which tags those are.
(Assignee)

Updated

4 years ago
Assignee: nobody → jlong
Whiteboard: u=dev c=mortar p=2 s=2013.9 → u=dev c=mortar p=2 s=2013.8
(Assignee)

Updated

4 years ago
No longer depends on: 872685
(Assignee)

Comment 1

4 years ago
I think this bug might be similar to a few other ones, but sole has gone ahead and rebuilt the list-detail template with x-tags which is awesome. We have a basic process in place now, but I want to keep this bug open to remind us to research better solutions for bundling x-tags.
Whiteboard: u=dev c=mortar p=2 s=2013.8 → u=dev c=mortar p=2 s=2013.9
(Assignee)

Comment 2

4 years ago
I think we are past the research phase; Leon has made a list of components that will be built: https://github.com/mozilla/app-components. bug 876028 has detailed discussion of how we are going to organize and deploy these deployments. I have looked at Polymer and the current x-tags to figure out how we should rebuild the current templates, with the conclusion that we need to really need to focus on a few components like scrollbox and made them work (too many tags are still in alpha phase).

Future will be represented by smaller bugs.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.