-
-
Notifications
You must be signed in to change notification settings - Fork 392
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
Artificial margin between proposal "header" and list of endorsements #2893
Comments
@deivid-rodriguez maybe we could move the attachments too? |
Yeah, probably, otherwise the list of attachments will probably get the same whitespace on top of it... |
Pinging @decidim/web-design |
This structure was built for longer content cases, and making sure the "voting block" would stay relatively on top on mobile devices. You could easily make the "List of endorsements" block part of the main column (thus avoiding the white gap), but you should probably reorganise the voting block for mobile devices with JS. |
I think I understand what you're saying @htmlboy. Moving attachments and endorsment list to the upper block means the voting sidebar will be rendered after that on mobile, and that's not good/intented. 👍 The current HTML structure still could be improved but maybe the quick fix for this is to set |
@deivid-rodriguez Height:0 sounds quite risky, since it won't probably force a scroll behaviour (or push other content) when the right column is longer than the main column. I'd test in several cases before using it… |
Maybe I should have mentioned @Crashillo and @javierarce 😅 |
I'm sure someone knows a good solution for this that works consistently across browsers. ☺ |
I'm taking a look at the markup in |
Seems like a better idea indeed. |
hi @Crashillo how is this going? |
I'm missing something here. Regarding as the piece of code you @deivid-rodriguez attached in the description, the commit moves the anchor and the partial inside the upper block. That's correct. Nevertheless, the code in This block belongs to a partial/widget/whateveryouwannacallit to render the adhesions list. In the design, that stuff could be found in the In any case, I remove the |
I only posted the diff here for discussion (just like I mentioned the alternative Some doubts remain however. What about the list of attachments as @mrcasals mentioned? What about the fact that the "button component" will appear after everything on mobile if we move the markup as @htmlboy noticed? Is that ok/intended? |
Hey, @decidim/lot-mods you should take a look at this |
To further clarify, in case someone is as confused as @Crashillo and I were: I posted the diff as a possible solution for discussion, but I didn't check the design app (assuming it was syncronized). It turns out that my diff coincidentally matches the approved markup in the design app, so that (understandably) confused @Crashillo. To sum up, this is a problem introduced when integrating the adhesions feature and should be fixed by proposing a PR to master with the mentioned diff. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. @carolromero & @xabier feel free to chime in. |
This is still pending /cc @decidim/lot-mods |
This is a Bug Report
🎩 Description
I see an excesive white space on top of the list of endorsements for a proposal. It seems like that whitespace is controlled by the height of the sidebar, which seems unexpected, since adding things to the sidebar will keep unintentionally increasing the whitespace...
Setting
height: 0
on the sidebar seems to do the trick on my browser, not sure what consequences that could have. However, the list of endorsements seemed "out of the markup structure" to me, the following patch in the template also had a similar visual effect of removing the whitespace. Not sure if that could have other negative consequences or break anything:📌 Related issues
📋 Additional Data
I can only reproduce this issue on chromium, but doesn't happen on firefox or chrome. Not sure about other browsers.
The text was updated successfully, but these errors were encountered: