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

Fix incorrect display of messages on multiple lines #226

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

lazy-sunshine
Copy link

@lazy-sunshine lazy-sunshine commented Oct 17, 2019

Fixes #12

UI changes done for same.

@rugk attaching screenshots for Ui display on diff screen width.Please suggest any changes if needed

Screen Shot 2019-10-17 at 11 45 39 PM

Screen Shot 2019-10-17 at 11 45 47 PM

Screen Shot 2019-10-17 at 11 45 54 PM

@rugk rugk changed the title #12 [Issue 12] Incorrect display of messages on multiple lines Fix incorrect display of messages on multiple lines Oct 17, 2019
@rugk
Copy link
Owner

rugk commented Oct 17, 2019

Hi @lazy-sunshine,
thanks for your first contribution to this project! 🎉 👍 🏅
I hope you'll like this project and enjoy hacking on it… 😃

I'll do a review soon and will later also test out the changes. But the screenshots look great/promising, already, thanks. 😃

Please do also note one important precautionary warning of me: In case you did not notice, you have committed (i.e. created commits) with potentially sensitive data like your (full/private) name or mail.
Anyone, who clones your fork/this repo can view these private details, exactly as you've committed them. Also, if this PR gets merged, this will stay in the (commit) history of this project and will thus hard to be removed later.

So if this was unintentional and you want that data to be changed/removed first, better do it now. 😃 Here is a good resource (actually from GitHubs help) on how to change your name/mail afterwards.
Also note that when setting your git username and especially your email, you can actually write/choose anything there. As for GitHub, it is recommend to use your GitHub username and – if you want to keep your mail private – the GitHub provided noreply address. You can even block pushes of commits with private mails.

So far just the possibilities. I just wanted to serve this as a friendly reminder, so you don't notice this only when it's too late. What you'll do depends solely on you. 😄

@rugk rugk added this to the v1.7 milestone Oct 17, 2019
@@ -223,6 +240,8 @@ a:active {
margin: 4px;
}


Copy link
Owner

Choose a reason for hiding this comment

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

Please remove these empty lines you've added. 😄

Copy link
Owner

Choose a reason for hiding this comment

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

ping

@@ -171,6 +173,21 @@ a:active {
margin-top: 8px;
}

@media screen and (max-width: 767px) {
Copy link
Owner

Choose a reason for hiding this comment

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

Hmm, a fixed break point… Is this really good?

I mean, it should automatically wrap depending on the browser size, so we likely need something (more) responsive there, because:

  1. in other languages, there may be more text, so even for >767px the text may wrap
  2. for other screen sizes (widths) and other text contents this whole point, where it needs to break may change, too

Generally, consider that the same code here is embedded for all places where such messages could be appear. Also, I likely will adapt/move it to all other add-on's too, as they use the same code. (see TinyWebEx/common#6)
So this should work at all screen sizes and with any content, if possible…

Copy link
Author

Choose a reason for hiding this comment

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

@rugk I dnt think its possible that I can change element css based on its sibling element having multiline text,
but I can do a mobile first approach i.e with a min-width media query and if the button does nt fit in single line due to small size then I will move it to next line else for all other cases it could be singleline css only.
please suggest otherwise

Copy link
Owner

Choose a reason for hiding this comment

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

Hmm I also dunno the best way. You could try to have a look on how Firefox implements it on addons.mozilla.org e.g. (look for an unsupported old extension e.g., that should have a red error message).
Or in Firefox itself (about:debugging or about:addons may be good canidates if you e.g. trigger an error).
Or in the source code… I've did search it in a similar area before, so maybe near here you can find something.


If you don't find a better way, yeah, maybe the mobile-first idea is the best. (if I understood your idea correctly)

@rugk
Copy link
Owner

rugk commented Oct 28, 2019

Uhm sorry for the late review, forgot to click to submit the review.

@rugk
Copy link
Owner

rugk commented Nov 7, 2019

@lazy-sunshine Are you still interested in completing this? If not, that's no problem, just add a notice, so I know what the current status of this PR is.

src/common/common.css Outdated Show resolved Hide resolved
@@ -171,6 +173,21 @@ a:active {
margin-top: 8px;
}

@media screen and (max-width: 767px) {
Copy link
Owner

Choose a reason for hiding this comment

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

Hmm I also dunno the best way. You could try to have a look on how Firefox implements it on addons.mozilla.org e.g. (look for an unsupported old extension e.g., that should have a red error message).
Or in Firefox itself (about:debugging or about:addons may be good canidates if you e.g. trigger an error).
Or in the source code… I've did search it in a similar area before, so maybe near here you can find something.


If you don't find a better way, yeah, maybe the mobile-first idea is the best. (if I understood your idea correctly)

Copy link
Owner

@rugk rugk left a comment

Choose a reason for hiding this comment

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

@lazy-sunshine If you need any pointers/help or have questions, feel free to ask.

@@ -223,6 +240,8 @@ a:active {
margin: 4px;
}


Copy link
Owner

Choose a reason for hiding this comment

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

ping

@rugk
Copy link
Owner

rugk commented Jan 23, 2020

@lazy-sunshine Are you still interested in completing this? If not, that's no problem, just add a notice, so I know what the current status of this PR is.

@rugk rugk modified the milestones: v1.7, 2.0 May 31, 2020
@rugk rugk modified the milestones: 1.8, next Nov 20, 2021
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.

Incorrect display of messages on multiple lines
2 participants