Merge ~ines-almeida/launchpad:update-wrapping-from-comment-boxes into launchpad:master

Proposed by Ines Almeida
Status: Merged
Approved by: Ines Almeida
Approved revision: 0c8999a9e095993d06b2aebb3f0eaa081d5ecbc9
Merge reported by: Otto Co-Pilot
Merged at revision: not available
Proposed branch: ~ines-almeida/launchpad:update-wrapping-from-comment-boxes
Merge into: launchpad:master
Diff against target: 29 lines (+4/-2)
1 file modified
lib/canonical/launchpad/icing/css/typography.scss (+4/-2)
Reviewer Review Type Date Requested Status
Colin Watson (community) Approve
Review via email: mp+440064@code.launchpad.net

Commit message

Updated <p> width restriction and increased 'page-width' parameter

Description of the change

Updated `lib/canonical/launchpad/icing/css/typography.scss` to remove max-width restriction for <p> text. Kept it for other components that had the same restriction.

Also updated the `page-width` scss parameter from 45em to 60em simply because it looks better imo. That parameter is only used in a few places.

To post a comment you must log in.
Revision history for this message
Ines Almeida (ines-almeida) wrote :

Whoever reviews, let me know if there are particular pages you think I should check/worry about.

Revision history for this message
Ines Almeida (ines-almeida) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

This is quite a big change to our rendering practice (despite the small diff). I personally prefer it, but let's see how it looks on qastaging and how it's received in terms of that "Wrap the text before the eye gets lost" comment. If it's too jarring, we might need to switch back to a finite but larger `max-width` instead.

review: Approve
Revision history for this message
Ines Almeida (ines-almeida) wrote :

> This is quite a big change to our rendering practice (despite the small diff).
> I personally prefer it, but let's see how it looks on qastaging and how it's
> received in terms of that "Wrap the text before the eye gets lost" comment.
> If it's too jarring, we might need to switch back to a finite but larger `max-
> width` instead.

I don't mind going for a more conservative approach and just wrapping later (perhaps using $wider-page as the value for the <p> wrap (which makes the comments wrap 66% later - 70em - which I think also looks pretty good).

I am writing this comment in the 'reply to comment' page and looking at your long-ish comment, and the more I think about it, the more I think it might be easily be jarring in pages where the text goes across the whole width of the page (such as the 'reply to comment' one).

I think by the end of this comment, I have convinced myself to change the approach ;)

Revision history for this message
Colin Watson (cjwatson) wrote :

I'm happy with this too.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/lib/canonical/launchpad/icing/css/typography.scss b/lib/canonical/launchpad/icing/css/typography.scss
2index 1e58f29..a2455d2 100644
3--- a/lib/canonical/launchpad/icing/css/typography.scss
4+++ b/lib/canonical/launchpad/icing/css/typography.scss
5@@ -1,6 +1,6 @@
6 // This file the result of auto-converting typography.css to scss.
7
8-$page-width: 45em;
9+$page-width: 60em;
10 $wider-page: $page-width + 15em;
11 $reduced-spacing: 0.8em;
12 $link-colour: #03a;
13@@ -39,13 +39,15 @@ h1, h2, h3, h4, h5, h6 {
14 p {
15 width: auto;
16 margin-bottom: $reduced-spacing;
17+ /* Wrap the text before the eye gets lost. */
18+ max-width: $wider-page;
19 }
20
21 div + p, ul + p, table + p {
22 margin-top: $reduced-spacing;
23 }
24
25- p, li, dt, dd, blockquote, .narrow, .narrow-listing {
26+ li, dt, dd, blockquote, .narrow, .narrow-listing {
27 /* Wrap the text before the eye gets lost. */
28 max-width: $page-width;
29 }

Subscribers

People subscribed via source and target branches

to status/vote changes: