Javascript browser compatibility, some utf-8 support, rebuild Virginia again #680
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attempts to close Virginia's #679 by implementing Javascript-aware web browser capabilities.
It's tested in Ubuntu and now Windows, with at least a partial fix for #584 -- though testing here is less thorough than I'd originally planned for that issue, it's also ... 14 months later, and test runs with about six states total were entirely successful.
Significant documentation and some code were lost between multiple production and dev environments in two operating systems. However, I've recreated most of the notes here describing all the paths I went down to ... avoiding what's in this pull request.