Skip to content
This repository has been archived by the owner on Dec 3, 2020. It is now read-only.

Fix deploy script and other changes. #215

Merged
merged 3 commits into from
Oct 26, 2018
Merged

Fix deploy script and other changes. #215

merged 3 commits into from
Oct 26, 2018

Conversation

Osmose
Copy link
Contributor

@Osmose Osmose commented Oct 26, 2018

This is a pile of tiny fixes that I'm comfortable self-reviewing in order to get a new release out tonight:

  1. Updates the deploy script to use the correct filename for the add-on file, which changed when we changed the add-on name. The 5.0.0 release failed due to this.
  2. Updates the preference subtree for overriding config values to use the new add-on ID; I missed this when switching to the new ID.
  3. I missed that the CSS changes earlier today made the empty onboarding view expand to an unreasonable width; the changes in this PR fix the width, and also ensure the onboarding view looks correct when the toolbar icon is pinned to the overflow menu.

@Osmose
Copy link
Contributor Author

Osmose commented Oct 26, 2018

Looked over the changes and tested them locally again, they look correct to me. self-r+

@Osmose Osmose merged commit 2daefd3 into master Oct 26, 2018
@Osmose Osmose deleted the fix-releases branch October 26, 2018 05:32
biancadanforth added a commit to biancadanforth/price-tracker that referenced this pull request Nov 5, 2018
… bounds

In previous PRs (mozilla#214, mozilla#215 and mozilla#218) CSS fixes were added to partially constrain either the whole popup or sections of it, leaving the 'Undo' section out. This patch puts a min-width and max-width on the whole popup, while flexibly sizing all its child containers, ensuring that the fixes applied in previous PRs remain in place.

Unfortunately, the Overflow menu has a width greater than our ideal popup width of 320px per the [UX spec](https://mozilla.invisionapp.com/share/UFNSHAIMT4V#/screens/317130676_Artboard_1), and that width cannot be controlled by a Web Extension, so I have set the max-width to 400px which will ensure the width of the popup doesn't change whether the toolbar button is in the overflow menu or not (previously, it would be one width when opened from the overflow menu and another width when opened otherwise).

One idea for the future is to try and detect whether the toolbar button is in the overflow menu or not and change classes accordingly via an experimental API, but that seems like overkill for now.
biancadanforth added a commit to biancadanforth/price-tracker that referenced this pull request Nov 6, 2018
… bounds

In previous PRs (mozilla#214, mozilla#215 and mozilla#218) CSS fixes were added to partially constrain either the whole popup or sections of it, leaving the 'Undo' section out. This patch puts a min-width and max-width on the whole popup, while flexibly sizing all its child containers, ensuring that the fixes applied in previous PRs remain in place.

Unfortunately, the Overflow menu has a width greater than our ideal popup width of 320px per the [UX spec](https://mozilla.invisionapp.com/share/UFNSHAIMT4V#/screens/317130676_Artboard_1), and that width cannot be controlled by a Web Extension, so I have set the max-width to 400px which will ensure the width of the popup doesn't change whether the toolbar button is in the overflow menu or not (previously, it would be one width when opened from the overflow menu and another width when opened otherwise).

One idea for the future is to try and detect whether the toolbar button is in the overflow menu or not and change classes accordingly via an experimental API, but that seems like overkill for now.
Osmose pushed a commit to Osmose/price-wise that referenced this pull request Nov 28, 2018
This overflow declaration was added in mozilla#215, nominally to help deal with
overflow issues when pinned to the overflow menu, but it's not clear how this
particular line helps vs the other changes to the width of the onboarding
view.

My theory on why this is biting us now:

- mozilla#256 updated the popup to a fixed width when not in the overflow menu, and a
  flexible width when it is.
- When we have more items than the 600px max height in the popup, we overflow
  and add a vertical toolbar inside.
- The vertical toolbar increases the desired width of the popup, causing the
  body element to add a horizontal scrollbar.
- The horizontal scrollbar increases the height beyond the 600px limit (since
  the initial overflow is contained within the product listing), causing the
  body element to add a vertical scrollbar.

If we force the body element to hide overflow, it refuses to add scrollbars, and
the overflow scrollbar on the product listing is overlaid correctly. This should
be safe to do now that we flex the width of the popup based on where it is
located.
Osmose pushed a commit to Osmose/price-wise that referenced this pull request Nov 28, 2018
This overflow declaration was added in mozilla#215, nominally to help deal with
overflow issues when pinned to the overflow menu, but it's not clear how this
particular line helps vs the other changes to the width of the onboarding
view.

My theory on why this is biting us now:

- mozilla#256 updated the popup to a fixed width when not in the overflow menu, and a
  flexible width when it is.
- When we have more items than the 600px max height in the popup, we overflow
  and add a vertical toolbar inside.
- The vertical toolbar increases the desired width of the popup, causing the
  body element to add a horizontal scrollbar.
- The horizontal scrollbar increases the height beyond the 600px limit (since
  the initial overflow is contained within the product listing), causing the
  body element to add a vertical scrollbar.

If we force the body element to hide overflow, it refuses to add scrollbars, and
the overflow scrollbar on the product listing is overlaid correctly. This should
be safe to do now that we flex the width of the popup based on where it is
located.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant