-
Notifications
You must be signed in to change notification settings - Fork 2
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
FFS-2295: Help modal #417
FFS-2295: Help modal #417
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opted to use a component here since there's now a Help
nav item in the main nav as well as a link in the Help banner.
<div class="usa-modal__content"> | ||
<div class="usa-modal__main padding-0 margin-0 maxw-none-important"> | ||
<div class="usa-modal__body padding-0"> | ||
<iframe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that I've resorted to an iframe here rather coding a bunch of JS. I figured this would more closely resemble our current approach and that we can add custom Mixpanel/New Relic events using Rails helpers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kinda a bummer to use an <iframe>
but I understand the complexity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I woudl investigate whether you could do this within the existing flash error/alert system :)
|
||
<ol> | ||
<% steps = t("help.show.#{topic}", default: {}).select { |k, _| k.to_s.start_with?('step') } %> | ||
<% steps.each do |step, _| %> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not use this _
thing :)
….com/DSACMS/iv-cbv-payroll into george/ffs-2295-help-modal
…ther than base_controller
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, pending the one last issue I noticed (the feedback form URL)
app/app/assets/stylesheets/cbv.scss
Outdated
// Button display handling based on device orientation and screen size | ||
.usa-button { | ||
&.display-block, | ||
&[class*="margin-bottom"] { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need to override the button display within the iframe, can we just give them a custom class name? I find it odd to have a selector like .usa-button[class*="margin-bottom"]
, since to me the "margin-bottom" class doesn't really have any connection to the "usa-button" class.
app/config/locales/en.yml
Outdated
search_keywords: Search your email for keywords like "payroll," "[Payroll Provider Name]," or "company ID." | ||
title: Check your welcome materials | ||
welcome_materials: Your company ID is often in your onboarding documents, welcome email, or payroll setup info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If designers are ok with the order these items are displaying in now, I guess you can ignore this.
app/app/assets/stylesheets/cbv.scss
Outdated
html { | ||
overflow: hidden; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this do anything? I don't think iframe contents can inherit like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does NOTHING. I was experimenting with some things and accidentally left it in there. The solution here was to set the scrolling
property on the iframe itself to false
. This approached worked, but it's actually deprecated.
app/config/locales/en.yml
Outdated
search_keywords: Search your email for keywords like "payroll," "[Payroll Provider Name]," or "company ID." | ||
title: Check your welcome materials | ||
welcome_materials: Your company ID is often in your onboarding documents, welcome email, or payroll setup info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sad this feedback didn't make it in!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eager for this redundant controller to be refactored away in follow up work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, it's actually going to be addressed in the follow up ticket that I'll start on today.
…account for sub-bullets, converted en.yml help config entries to have a content property
…ow-use-new-database * origin/main: FFS-2295: Help modal (#417)
Ticket
Resolves FFS-2295.
/help
route to use in iframeHelp
link in top nav that triggers the Help ModalChanges
Context for reviewers
Acceptance testing
:alert: Deploy block! @ffs-eng I just merged PR [#123] and will be doing acceptance testing in demo - please don't deploy until I'm finished!
)