Build Out Backend DOM Search about find

[brandon1024]

Arch Doc

Moved to GitHub Wiki, API Specification

Supporting Dynamic Web Pages

What happens if we parse the DOM and build our model object, but the web page is dynamic and changes elements, layout, or text content? We will need to ensure that if we encounter this situation, we handle it appropriately. If an element is not found in the web page that exists in our model object, do we skip that occurrence? Or do we make an attempt to rebuild the model object?

Revision

Because web pages have vastly varying DOMs, it is very likely that rigorous testing will need to happen to make this work. For instance, we will want to filter out certain types of elements that can contain text, but that do not appear in the web page (script element for example). It is very important to keep our code modular for allowing us to add in these refinements in the future.

Documentation (_{^{Add useful links here!}})

• Long Lived Connections: Google, Message API
• More on Messaging: Thoughtbot, Message API
• List of HTML Elements: W3
• List of DOM methods: W3
• DOM TreeWalker: MDN
• DOM nodeType Property: W3
• Whitespace Text Nodes in DOM: MDN

The last step requiring js to highlight text should be "done". The only issue remaining after the parsing is completed would be to tweak the existing highlight.js

[brandon1024]

@MikeWalz11 It might require some pretty heavy modifications though. I have't really looked into it much yet, but once I finish the rest, you can dive into it!

[brandon1024]

Finally seeing some progress!

[brandon1024]

Progress: develop...F9-Build-Backend-DOM-Search

PR Merged: #55