Closed
Bug 976854
Opened 10 years ago
Closed 10 years ago
select browser CSS toolkit
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(firefox34 fixed)
RESOLVED
FIXED
mozilla34
Tracking | Status | |
---|---|---|
firefox34 | --- | fixed |
People
(Reporter: dmosedale, Assigned: dmosedale)
References
Details
I think the easiest things to do here would be Twitter Bootstrap, nothing at all, or some way to reuse Australis styles in our internal iframes (perhaps pulling them in via chrome: or jar: URIs?). That's in order of difficulty.
Assignee | ||
Comment 1•10 years ago
|
||
https://webrtc-apps.etherpad.mozilla.org/109 has some good analysis of our needs w.r.t. Twitter bootstrap. It'd be interesting to hear from mconley what sort of options we might have for re-using Australis styles in content <browser> or <iframe> elements. It might be advantageous to simply punt on this decision, start with hand-styling, and then pull in something later if needed.
Blocks: 974875
Comment 2•10 years ago
|
||
I'll give this some further thought, but I'll come right out and say that the Australis styles were not really designed to apply to content. I think that's going to be a long haul. But needinfo'ing myself so that I can let it percolate in my head for a night.
Flags: needinfo?(mconley)
I'd personally suggest to go with nothing at all for the MLP (just basic handcrafted styles, rough webdesign just to prove it works) and postpone making the CSS tooling decision after that.
Comment 4•10 years ago
|
||
I'd suggest that'd probably be the best way forward. Attempting to untangle the Australis toolbar / panel stylings into things that can be brought into content is not a trivial undertaking.
Flags: needinfo?(mconley)
Assignee | ||
Comment 5•10 years ago
|
||
I agree. CSS is easy to mixin later, and we're starting with something pretty straightforward.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → dmose
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
I don't think this needs QA before we release. Please needinfo me to request specific testing.
Whiteboard: [qa-]
What's the correct target milestone here?
Flags: qe-verify-
Flags: needinfo?(dmose)
QA Contact: anthony.s.hughes
Whiteboard: [qa-]
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(dmose)
Target Milestone: --- → mozilla34
status-firefox34:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•