Lib Joshua Martinito
Lib Joshua Martinito
@rohitpaulk could you please take a look at the approach before i go through the broken tests?
not sure if i should add information about keyboard navigation and how that would look like (small notes near each button/group of buttons? one info icon with a tooltip at...
(a) fixed (b) fixed. since we're adding a 'continue or step back' block after submitting an answer, i think that pressing backspace to return to the previous block should only...
updates: - added indicator for focus state for buttons - removed backspace for returning to previous block group to keep consistent, tab to move to button + enter or space...
for the hard-scroll, i can't replicate it after recently testing on master vs vercel deployments. maybe this could be a separate task if it persists?
had to remove tests for navigation. problems were with how ember-cli-page-object behaves: - for j/k: `triggerable` + keydown event doesn't accept lowercase keys - for Enter: `triggerable` + keydown requires...
can you please confirm if it's fine to ignore breaking tests for now
to avoid making changes to tester versions at this stage, what do you think of keeping around slug? then instead of checking if there are no null course stage slug...