Skip to content

Conversation

@sjwmoveon
Copy link
Contributor

Just about everything is either tied to a particular object ID that's only on the new page or otherwise doesn't apply to existing pages.

Copy link
Contributor

@technicalex technicalex left a comment

Choose a reason for hiding this comment

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

Looks good! Just a reminder about a change you already made elsewhere :)

Copy link
Contributor

@codygordon codygordon left a comment

Choose a reason for hiding this comment

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

I can't see the Figma, if you're able to share it. Just have some subjective design feedback: it's hard to tell the survey input is an input as it's white on white, and the Yes/No radio at the bottom looks a bit crowded and some margin-top on it would help!

@sjwmoveon
Copy link
Contributor Author

The background was supposed to be light blue, thanks for catching that! I made a mistake trying to fix something with the templateset, should be better now. Added a little extra spacing for the radio buttons as well.

@sjwmoveon sjwmoveon requested a review from technicalex March 1, 2022 18:52
Copy link
Contributor

@technicalex technicalex left a comment

Choose a reason for hiding this comment

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

Looks good!

@sjwmoveon
Copy link
Contributor Author

[On pause while I address feedback from Bri]

@sjwmoveon
Copy link
Contributor Author

I had to make a few additional changes; requesting feedback again. Thanks!

Copy link
Contributor

@technicalex technicalex left a comment

Choose a reason for hiding this comment

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

Just a few questions. Thanks!

@@ -0,0 +1,4 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
Copy link
Contributor

Choose a reason for hiding this comment

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

Similar question to the one I left in the ak-template-set pull request: is this file used anywhere? If so, I can't seem to find it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ak-template-set instead includes the .html version, but it still seemed useful to have it in Giraffe too. If you think it's best to just leave in ak-template-set I can delete here.


html {
width: 100vw;
scroll-padding-top: 57px;
Copy link
Contributor

Choose a reason for hiding this comment

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

I wasn't familiar with this style, so I looked it up. I think it only applies when we are using scroll snap, which I can't find either in existing styling or in these changes. Maybe I'm missing something; can you please explain? Thank you!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

On mobile, there's a button that lets you jump to the form, but because the header floats above everything else on the page, the form gets cut off. Adding the padding here makes the anchor tag jump to the right place to display the entire form.

Copy link
Contributor

Choose a reason for hiding this comment

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

FYI @sjwmoveon, new scroll-padding-top values should be used for compatibility with the new header if this pull request is merged. I've copied the correct values below. (I suppose only the first one applies, if the button to jump will only ever appear on mobile.) Thank you!

  html {
    scroll-padding-top: 145px;
  }
  @media (min-width: 768px) {
    html {
      scroll-padding-top: 149px;
    }
  }
  @media (min-width: 1025px) {
    html {
      scroll-padding-top: 102px;
    }
  }

$moriginal-blue-medium: #296ecb;
$c-facebook: #3B5998;
$c-twitter: #1DA8E2;
$c-twitter: #1DA8E2;
Copy link
Contributor

Choose a reason for hiding this comment

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

This color doesn't appear to be used. Furthermore, it looks like it's a different color from the color specified on Figma (#5AA5EB) and also (confusingly!) different from both the button and hover color I was asked to use for the Twitter button on my page (#1DA1F2 and #3FB6FF). If it's not being used, I would recommend removing it, unless we expect to use it in the future. But maybe more importantly, should we ask for clarification on the correct Twitter color?

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 didn't actually add this, just a newline at the end of the file. But yes, that's very confusing and we should ask for clarification. (Maybe it's used on existing main-giraffe template pages?)

@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug C 1 Bug
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

No Coverage information No Coverage information
0.0% 0.0% Duplication

@codygordon codygordon removed their request for review March 3, 2023 16:42
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.

4 participants