Closed Bug 1243403 Opened 9 years ago Closed 9 years ago

Implement the general design of the responsive design mode

Categories

(DevTools :: Responsive Design Mode, defect, P1)

defect

Tracking

(firefox47 fixed)

RESOLVED FIXED
Firefox 47
Iteration:
47.1 - Feb 8
Tracking Status
firefox47 --- fixed

People

(Reporter: gl, Assigned: gl)

References

Details

(Whiteboard: [multiviewport] [mvp-rdm])

Attachments

(2 files, 6 obsolete files)

We should implement the basic design of the responsive design mode whether that means centering it, adding the appropriate background colour, etc.
Flags: qe-verify-
Blocks: 1237360
Whiteboard: [multiviewport] → [multiviewport] [triage]
Assignee: nobody → gl
Attached patch 1243403.patch (obsolete) (deleted) — Splinter Review
Attachment #8712831 - Flags: review?(jryans)
Attached image Screenshot (obsolete) (deleted) —
Attachment #8712832 - Flags: ui-review?(hholmes)
Attached image general-single-viewport-notes.png (deleted) —
Added a screenshot with general notes, repeated here:

- Border on the viewport should be: border: 1px solid #DDE1E4;
- Text-shadow on the viewport: text-shadow: 0 4px 4px 0  rgba(155, 155, 155, 0.26);
- The top area is ~16px tall.
- background of the top area is #fcfcfc;
- the color in the top area is #696969;
- the border of the top area is the same as the rest of the viewport.

Also:

Corners on the viewport are /not/ rounded.
Corners on the top menu area /are/ rounded. (Border-radius 1px).
Comment on attachment 8712832 [details]
Screenshot

Added screenshot + notes above!
Attachment #8712832 - Flags: ui-review?(hholmes) → feedback?
Attachment #8712831 - Flags: review?(jryans)
Another note (sorry):

Background should be var ----theme-body-background.
Attached patch 1243403.patch [1.0] (obsolete) (deleted) — Splinter Review
Attachment #8712831 - Attachment is obsolete: true
Attachment #8712850 - Flags: ui-review?(hholmes)
Attachment #8712850 - Flags: review?(jryans)
Attached image Screenshot - Light Theme (obsolete) (deleted) —
Attachment #8712832 - Attachment is obsolete: true
Attachment #8712832 - Flags: feedback?
Attached image Screenshot - Dark Theme (obsolete) (deleted) —
I think one of the things we need to think about is how it should look like on the dark theme.
Comment on attachment 8712850 [details] [diff] [review]
1243403.patch [1.0]

Review of attachment 8712850 [details] [diff] [review]:
-----------------------------------------------------------------

I heavily think we should avoid using hardcoded colors, especially if we want the responsive mode shell to adapt to themes.

Bug 1242709 makes our theme colors much closer to the ones used in this patch.
Attachment #8712850 - Flags: feedback-
Attached patch 1243403.patch [2.0] (obsolete) (deleted) — Splinter Review
Attachment #8712850 - Attachment is obsolete: true
Attachment #8712852 - Attachment is obsolete: true
Attachment #8712853 - Attachment is obsolete: true
Attachment #8712850 - Flags: ui-review?(hholmes)
Attachment #8712850 - Flags: review?(jryans)
Attachment #8712887 - Flags: review?(jryans)
Attachment #8712887 - Flags: feedback?(ntim.bugs)
Comment on attachment 8712887 [details] [diff] [review]
1243403.patch [2.0]

Review of attachment 8712887 [details] [diff] [review]:
-----------------------------------------------------------------

r+ assuming ntim agrees, he knows the theme colors much better than me.
Attachment #8712887 - Flags: review?(jryans) → review+
Comment on attachment 8712887 [details] [diff] [review]
1243403.patch [2.0]

Review of attachment 8712887 [details] [diff] [review]:
-----------------------------------------------------------------

Minor comment about CSS organisation:
I think we should start adding headers like on the memory tool CSS [0] to clearly separate each section of the CSS, like this:
/**
 * Viewport container
 */
This will help us keep our CSS clean, especially when more rules are added.

[0]: https://dxr.mozilla.org/mozilla-central/source/devtools/client/themes/memory.css#134

::: devtools/client/responsive.html/index.css
@@ +26,1 @@
>  iframe {

I would prefix this selector with .viewport to explicit what we're actually styling here.
Attachment #8712887 - Flags: feedback?(ntim.bugs) → review+
(In reply to Tim Nguyen [:ntim] from comment #12)
> ::: devtools/client/responsive.html/index.css
> @@ +26,1 @@
> >  iframe {
> 
> I would prefix this selector with .viewport to explicit what we're actually
> styling here.

Good idea, or can also replace with ".browser" (which is on the iframe).
(In reply to Tim Nguyen [:ntim] from comment #12)
> Comment on attachment 8712887 [details] [diff] [review]
> 1243403.patch [2.0]
> 
> Review of attachment 8712887 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> Minor comment about CSS organisation:
> I think we should start adding headers like on the memory tool CSS [0] to
> clearly separate each section of the CSS, like this:
> /**
>  * Viewport container
>  */
> This will help us keep our CSS clean, especially when more rules are added.

Yes, it seems fine for now.  Like the TODO says at the top, I think we may switch to CSS file per component once we have utility to load them easily.  But for now, comments are a good way.
Attached patch 1243403.patch [3.0] (deleted) — Splinter Review
Attachment #8712887 - Attachment is obsolete: true
Attachment #8712909 - Flags: review+
https://hg.mozilla.org/mozilla-central/rev/1c2c044db3ef
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 47
Iteration: --- → 47.1 - Feb 8
Priority: -- → P1
Whiteboard: [multiviewport] [triage] → [multiviewport]
Whiteboard: [multiviewport] → [multiviewport] [mvp-rdm]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: