Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream #10

Merged
merged 45 commits into from Jul 5, 2022
Merged

Upstream #10

merged 45 commits into from Jul 5, 2022

Conversation

decabeza
Copy link
Collaborator

@decabeza decabeza commented Jul 4, 2022

Objectives

  • Bump rails from 5.2.6 to 5.2.7.
  • Bump Rails from 5.2.7 to 5.2.7.1.
  • Move banner styles to their own stylesheet.
  • Fix banner link on Chromium 101.
  • Allow send newsletters with images.
  • Fix margins on header content.
  • Update deploy-secrets.yml.example.
  • Monitor CONSUL with monit.
  • Improve subnavigation styles on mobile screens.
  • Fix deployment error after adding monit.
  • Fix link to comments on admin view for debates.
  • Add new tags on legislation markdown.
  • Fix subnavigation dropdown menu styles.
  • Fix homepage feeds participation layout.
  • Update custom nl text.
  • Add unsubscribe info on system emails.
  • Fix debate show votes alignment.
  • Fix draft comments button alignment.
  • Update custom texts.
  • Show progress bar for all budgets.
  • Replace budget feeds date phase.
  • Show participation not allowed message on mobile.
  • Add wysiwyg to poll description and summary.
  • Add read less button on poll header.
  • Fix data-toggle on poll answer description.
  • Add background color to mobile menu.

decabeza and others added 30 commits May 3, 2022 20:44
Since we've already got a banner component, we follow the convention of
using one CSS file per component. We also reduce the number of lines in
the huge layout.scss file.

Now the sections in layout.scss from "17" to "19", just like they jump
from "08" to "10".
After upgrading to Chrome/Chromium 101, the test "Cross-Site Scripting
protection banner URL" was failing with the message:

Element <a>...</a> is not clickable (...) Other element would receive
the click: <div class="banner" style="background-color:#FF0000;">...</
div>

The reason was that, when using the structure of a link with one <h2>
and one <h3> inside, previous versions of Chrome/Chromium considered the
margin between the <h2> and the <h3> part of the link.  Version 101 does
the same thing Firefox does and so clicking on the space between the
<h2> and the <h3> doesn't result in clicking the link.

In order to keep the previous behavior, we're adding a `display: block`
tag to a link.

Note that, in the future, we might change the structure of the banner,
since using <h3> as a subheading is discouraged by the W3C, and we
aren't sure about the usability of making the whole banner clickable.
But, for now, we're just fixing the issue so our test suite is green
again.
Improve subnavigation styles on mobile screens
Fix deployment error after adding monit
Fix link to comments on admin view for debates
Fix subnavigation dropdown menu styles
Fix homepage feeds participation layout
@decabeza decabeza merged commit 70aa785 into master Jul 5, 2022
@decabeza decabeza deleted the upstream branch July 5, 2022 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants