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

[#10941] Copying questions requires scrolling the whole list of current questions #10961

Merged

Conversation

Jellwood
Copy link
Contributor

Fixes #10941

PR Checklist

Outline of Solution

The footer was attached by moving all of the styling of the modal footer and the table in the modal window within the super CSS file for the modal window for copying. Once the footer was the appropriate width, the height was fixed to allow for a table border the same height so that the footer does not interfere with the last question. The behavior was preserved from the clip shown in the issue and the table did not change any functionalities.

@teammates-bot
Copy link

Hi @Jellwood, these parts of your pull request do not appear to follow our contributing guidelines:

  1. PR Title
    • Issue Reference (#<issue-number>) missing.

@Jellwood Jellwood changed the title [10941] Copying questions requires scrolling the whole list of current questions [#10941] Copying questions requires scrolling the whole list of current questions Feb 13, 2021
@madanalogy
Copy link
Contributor

madanalogy commented Feb 15, 2021

Hello thanks for contributing to teammates! Could you please record a short gif/video demonstrating your fix for the modal?

@madanalogy madanalogy added the s.Ongoing The PR is being worked on by the author(s) label Feb 15, 2021
@Jellwood
Copy link
Contributor Author

Hi! I am so sorry about that, this GIF shows the process of copying a question in addition to scrolling through the table until the end to show the table formatting, and finally selecting to ensure that the functionality still works!

TeammatesWorkingStickyFooter

@madanalogy madanalogy added s.ToReview The PR is waiting for review(s) and removed s.Ongoing The PR is being worked on by the author(s) labels Feb 16, 2021
Copy link
Contributor

@t-cheepeng t-cheepeng left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@Derek-Hardy Derek-Hardy left a comment

Choose a reason for hiding this comment

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

The code looks fine to me.

However, the original issue has another small checkbox fix proposal.

You can either attempt it here or modify PR description to 'Part of #10941'.

@Jellwood
Copy link
Contributor Author

Sorry about that, I'll try to get it working and having the checkboxes size up

@madanalogy madanalogy added s.Ongoing The PR is being worked on by the author(s) and removed s.ToReview The PR is waiting for review(s) labels Feb 16, 2021
@Jellwood
Copy link
Contributor Author

I was able to get the checkbox elements to a larger size for Chrome, I tested using Chrome and Firefox, and the boxes are similar sizes in both browsers. I was able to replicate the smaller checkbox sizes in Chrome, and I used that as the baseline. I do not have access to Safari to ensure that it works in this browser, and I can build in my Windows environment this weekend as well to make sure that Internet Explorer also works with these new additions if needed. The GIF below shows my Firefox browser then my Chrome browser to show that both browsers are displaying similar sized checkboxes.
TeammatesBoxesFirefoxChrome

@madanalogy madanalogy added s.ToReview The PR is waiting for review(s) and removed s.Ongoing The PR is being worked on by the author(s) labels Feb 19, 2021
Copy link
Contributor

@Derek-Hardy Derek-Hardy left a comment

Choose a reason for hiding this comment

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

Checkbox scaling looks good to me.

td {
text-align: center;
vertical-align: middle;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not entirely sure the central alignment improves the readability. I will leave this to other reviewers' opinions.

Original:
Screenshot 2021-02-19 at 13 34 55

After:
Screenshot 2021-02-19 at 13 35 41

Copy link
Contributor

Choose a reason for hiding this comment

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

Speaking for myself: I'd prefer the original look. That allows reading in a more natural manner.

Copy link
Contributor

Choose a reason for hiding this comment

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

For UI decisions such as this one, best to check with @damithc

Copy link
Contributor

Choose a reason for hiding this comment

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

Previously we have standardized that such tables with text should be left-aligned (i.e. original)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can make those changes and have them in tomorrow if need be. That was my bad, I forgot that the earlier demo questions tended to have shorter questions that appeared to have centered check boxes and I did not want to break that alignment in adding scaling. If the original left-aligned is the standard, I can go back and make sure everything fits that standard.

Copy link
Contributor

Choose a reason for hiding this comment

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

@t-cheepeng was involved in standardizing this kind of UI issues. @t-cheepeng do we have a document of the decisions taken? If not, we should.

Copy link
Contributor

Choose a reason for hiding this comment

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

@damithc Yes, we do have a document for this. But it was not made made public/posted on github

Copy link
Contributor

Choose a reason for hiding this comment

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

@damithc Yes, we do have a document for this. But it was not made made public/posted on github

I see. Let's add it to our docs. At least a public link to the Google doc.

@Derek-Hardy Derek-Hardy added s.FinalReview The PR is ready for final review and removed s.ToReview The PR is waiting for review(s) labels Feb 19, 2021
@Derek-Hardy Derek-Hardy added s.Ongoing The PR is being worked on by the author(s) and removed s.FinalReview The PR is ready for final review labels Feb 19, 2021
@t-cheepeng t-cheepeng added s.ToReview The PR is waiting for review(s) and removed s.Ongoing The PR is being worked on by the author(s) labels Feb 22, 2021
@madanalogy madanalogy self-assigned this Feb 22, 2021
@madanalogy madanalogy added c.Bug Bug/defect report s.ToMerge The PR is approved by all reviewers including final reviewer; ready for merging c.Feature User-facing feature; can be new feature or enhancement to existing feature and removed s.ToReview The PR is waiting for review(s) c.Bug Bug/defect report labels Feb 22, 2021
@madanalogy madanalogy added this to the V7.11.0 milestone Feb 22, 2021
@madanalogy madanalogy merged commit d1d7916 into TEAMMATES:master Feb 22, 2021
@madanalogy
Copy link
Contributor

Thank you for your contribution! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c.Feature User-facing feature; can be new feature or enhancement to existing feature s.ToMerge The PR is approved by all reviewers including final reviewer; ready for merging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Copying questions requires scrolling the whole list of current questions
7 participants