Extended Description
As a user, I would like my browser to not lock up when I apply FedRAMP validation rules, so I have a normal web experience.
Context: SaxonJS processes XSLT synchronously, without yielding back until processing is complete. As a result, the browser locks up when processing. Alternatives would involve running in a web worker or similar, running server-side, or taking mitigation steps such as lowering user expectations so they are not surprised when the browser locks. Previously, web-workers were ruled out due to lack of available DOM APIs. This ticket is to look for alternative approaches that will improve the user experience.
Acceptance Criteria
[ ] User experience improved when validating documents
[ ] Improvements documented in appropriate form
Definition of Done
[ ] Acceptance criteria met
[ ] Unit test coverage of our code > 90% - needs automation story
[ ] Accessibility tests pass - needs automation story
[ ] Automated code quality checks pass
[ ] Security reviewed and reported - check in with Wes on what we could do here
[ ] Reviewed against plain language guidelines
[ ] Design QA passed
[ ] Code must be self-documenting
[ ] No local tech debt
[ ] Documentation updated
[ ] Architectural Decision Record completed as necessary for significant design choices
Extended Description As a user, I would like my browser to not lock up when I apply FedRAMP validation rules, so I have a normal web experience.
Context: SaxonJS processes XSLT synchronously, without yielding back until processing is complete. As a result, the browser locks up when processing. Alternatives would involve running in a web worker or similar, running server-side, or taking mitigation steps such as lowering user expectations so they are not surprised when the browser locks. Previously, web-workers were ruled out due to lack of available DOM APIs. This ticket is to look for alternative approaches that will improve the user experience.
Acceptance Criteria
Definition of Done