Bug: Mobile "follow" menu overlapping issue #179
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #177.
The Good News
The simple bug fix of the mobile "follow" menu overlapping text was actually already identified and fixed in the parent theme already in v4.5.1 . So, this should be as simple as updating the theme in this website to >= v4.5.1, however...
The Bad News
Upgrading the theme to >=v4.5.1 causes some layout issues that appear to have been completed with intent in the parent theme due to certain dependencies of the parent theme being updated. It appears as though these layout changes mostly affect Desktop widths from what I can observe. For example, after an upgrade to v.4.6.0 you can see how the layout for articles change on desktop below:
Compare that to the current production site:
so you can see how much "thinner" the main content width is. Do you like or don't like that? In my opinion it kinda made the left/right aligned images look weird to me, maybe because they seem bigger?
I'll assume the "thinner" content isn't desired and you would like to utilize cleanly the maximum real estate on the page without so much white space? So, I did include some additional "parent over-ride" CSS for the short term. I'm not really liking doing this, but I'm not sure how else to handle. I can try to create a pull request upstream to the parent theme, but given this was done intentionally, that solution will probably take longer to put together as it will require a lot of theme re-work I'm afraid to try and generalize a compromised solution.
We can also accept the new layout and manually re-size the affected images that don't look great? Maybe that's better than adding over-ride CSS?
Do you have any thoughts, ideas, or preferences on how you would like to handle?