Skip to content

Conversation

tofumatt
Copy link
Contributor

@tofumatt tofumatt commented Jun 14, 2017

Adds support for themes on the desktop site and fixes issues from the last update.

This also improves the HTML and CSS used to create the same page for extensions (#2430).

Mobile

screen shot 2017-06-14 at 00 52 28

screen shot 2017-06-14 at 00 52 32

screen shot 2017-06-14 at 00 57 59

screen shot 2017-06-14 at 00 58 01

Desktop

screenshot 2017-06-14 00 58 06

-----------------

screenshot 2017-06-14 00 57 55

@tofumatt tofumatt requested a review from kumar303 June 14, 2017 00:01
@tofumatt tofumatt requested review from muffinresearch and removed request for kumar303 June 14, 2017 09:40

const descriptionSanitized = sanitizeHTML(
nl2br(description), allowedDescriptionTags);
const summarySanitized = sanitizeHTML(addon.summary, ['a']);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these vars only used once? If so it might be nice to keep the use of the sanitization function closer to the dangerouslySetInnerHTML prop usage?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The thought I was having is that it might make it easier to have a future lint rule that all content passed as HTML via dangerouslySetInnerHTML. should be wrapped in a sanitization function.

@muffinresearch
Copy link
Contributor

This can be a follow-up but I think there's some breakpoint tuning needed - it could probably stay 100% width longer see:

add-ons_for_firefox

@tofumatt
Copy link
Contributor Author

I'll see about the breakpoints or setting min-widths on those left sections really quickly, good catch.

@muffinresearch
Copy link
Contributor

muffinresearch commented Jun 14, 2017

There's some small rtl issues at the similar width:

xo i _ o _suo-pp

Not sure why the RTL debug lang chars are broken there (see the bottom) - maybe those glyphs don't exist in the font?

Copy link
Contributor

@muffinresearch muffinresearch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of additional points. I wonder if there should be a max-width for the main content? On a really large screen the content get's so wide it's hard to read.

Another one to maybe follow-up on - should the read-more link be turned off on desktop?

Really looking nice!

r+wc

@tofumatt
Copy link
Contributor Author

I wondered about content max-width but I say let the actual page expand as much as possible... max-width can also hide issues with display or make things hard to account for in my experience. But prose like the details should wrap after around 500px so I'll look into doing that in a follow-up.

Read more like being off on desktop probably makes sense, although when we start adding more boxes underneath it might be useful; add-on descriptions can be wildly long and it will dominate that section of the page.

@tofumatt
Copy link
Contributor Author

Not sure why coveralls is complaining but coverage for those files is still at 100% and I didn't really touch much code even so merging...

@tofumatt tofumatt merged commit 615feb0 into master Jun 14, 2017
@tofumatt tofumatt deleted the themes-2559 branch June 14, 2017 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants