31
edits
Compatibility/Tripwire: Difference between revisions
status update
Twisniewski (talk | contribs) (Added Q1 2017 KRs) |
Twisniewski (talk | contribs) (status update) |
||
| Line 79: | Line 79: | ||
1. Page snapshot creation | 1. Page snapshot creation | ||
a. recording the raw network requests and responses | a. recording the raw network requests and responses (done) | ||
b. recording the initial and final session state | b. recording the initial and final session state (partly done [1]) | ||
c. recording inner window size | c. recording inner window size (done) | ||
d. recording and storing which system fonts were used | d. recording and storing which system fonts were used | ||
e. writing a user-accessible snapshot file to the filesystem | e. writing a user-accessible snapshot file to the filesystem (done) | ||
f. recording plugin versions | f. recording plugin versions | ||
2. Result snapshot creation | 2. Result snapshot creation | ||
a. opening the given snapshot with initial state (window size, session, etc) and detecting when it has "loaded" | a. opening the given snapshot with initial state (window size, session, etc) and detecting when it has "loaded" (partly done [2]) | ||
b. sandboxing networking requests to the list in the page snapshot | b. sandboxing networking requests to the list in the page snapshot (done) | ||
c. recording unexpected resource access | c. recording unexpected resource access (partly done [3]) | ||
d. recording a screenshot of the final page | d. recording a screenshot of the final page (done) | ||
e. recording the final frame tree/display list | e. recording the final frame tree/display list (done) | ||
f. recording the final "frozen" DOM state as an HTML file | f. recording the final "frozen" DOM state as an HTML file | ||
g. writing a user-accessible snapshot file to the filesystem | g. writing a user-accessible snapshot file to the filesystem (done) | ||
3. Result snapshot comparison | 3. Result snapshot comparison | ||
a. comparing the frame tree of two results and giving a pass/fail result | a. comparing the frame tree of two results and giving a pass/fail result (partly done [4]) | ||
b. presenting frame trees of both results for comparison | b. presenting frame trees of both results for comparison (partly done [5]) | ||
c. presenting screenshots of both results for comparison | c. presenting screenshots of both results for comparison (done) | ||
d. presenting the frozen DOM results, with links from the frame tree to the nodes they represent | d. presenting the frozen DOM results, with links from the frame tree to the nodes they represent | ||
e. summarizing unexpected network fetches, missing system fonts, plugins, web console output, full network log | e. summarizing unexpected network fetches, missing system fonts, plugins, web console output, full network log | ||
[1] due soon. only the cookies are being stored (as part of network requests). | |||
[2] still needs better heuristics for detecting when page has "loaded". | |||
[3] there are still bugs with ads not being recorded properly, so coming up as "unexpected". | |||
[4] have a diff-like interface; need to decide what types of diffs count as passes/fails. | |||
[5] showing side-by-side diffs already, but it's still very rudimentary. | |||
Estimate of overall progress toward meeting OKRs: 60-70% | |||
[[Category:Web Compatibility]] | [[Category:Web Compatibility]] | ||