* Implemented image restore from rr_dataURL
* Implement saving images in the snapshot
* Fixed image saving, added a test
* Rename data-src to data-rrweb-src
* Updated the guide
* Rename recordImages to inlineImages and try catch
* A fix, some tweaks and 2 new log warnings
* Handle CORS errors when reading CSS rules
* Fix after merge
* Improve try catch for the inline image
* PR comments tweaks
* Fix typescript lint
* Small tweaks
* Fix a log warning
* Implemented image restore from rr_dataURL
* Implement saving images in the snapshot
* Fixed image saving, added a test
* Rename data-src to data-rrweb-src
* Updated the guide
* Rename recordImages to inlineImages and try catch
* create rrdom package
* test(rrdom): add unit tests for polyfill.ts
* fix(rrweb snapshot): type check errors
Errors are caused by the declaration similarity of @types/mocha and @types/jest if we install both of them in the whole project.
* Set tagNames to upper case by default
This mirrors the `Element.tagName` implementation:
```
For DOM trees which represent HTML documents, the returned tag name is always in the canonical upper-case form. For example, tagName called on a <div> element returns "DIV".
```
https://developer.mozilla.org/en-US/docs/Web/API/Element/tagName
* Add workspace file
* VSCode settings for rrdom tests
* Add basic test for RRDocument
* Only setup jest tests for rrdom
* mock Node type and Event type for nodejs environment
* test(rrdom): add snapshot for document.test.ts
* fix issue of nwsapi import and add unit tests for rrdom
* fix: querySelectorAll returns nothing when querying elements with ids and classNames
* fix: error of unit test for Event polyfill
Since Event class is built in nodejs after v15.0.0
* add a dummy implementation of canvas
* add style element support
* add unit test for style element
Co-authored-by: Justin Halsall <Juice10@users.noreply.github.com>
- this had the effect of making things visible which should have been invisible
- not sure what I was thinking with 'potentially non-standard browsers', maybe I thought I was covering return values from getPropertyValue of null or false. Could potentially add explicit tests for null or false, but as there is no evidence for these non-standard browsers, leaving as-is
