Web compatibility has several layers. A screenshot can demonstrate layout progress without proving that the page’s controls, selection or saved state work.
What changed between the two reports
The July 31 report on Servo 0.4 describes improvements affecting sites such as lichess and Zulip, plus pointer capture and SharedWorker support. Google Photos and Cash Converters had already worked before that release. Experimental features in the report should not be read as universally enabled compatibility.
The August 31 report introducing 0.5 adds Linux aarch64 binaries and lowers Android’s requirement from 13 to 10. It shows further page fixes, including Gumroad rendering, and security updates. Text selection becomes visible, but interactive selection is still described as forthcoming. A painted highlight is not proof that a user can drag to select text.
A small acceptance matrix is more useful than a screenshot
For a page you need, define one concrete task before comparing engines. A product page might require opening a variant selector, changing the quantity and retaining that choice. A collaboration page might require keyboard focus, text entry and successful submission. Merely recognizing the layout cannot establish those behaviors.
Record each stage separately: content appears, layout stays usable, input reaches the intended control, and the application retains or submits the resulting state. If the final stage fails, keep the earlier successes in the record without calling the task complete. This makes a bug report more informative than a single overall “works” label.
Keep the test reproducible
Specify Servo version, operating system, page URL and the smallest sequence that reproduces a failure. Separate a server login error from a rendering or input failure. Avoid attaching account tokens or private session data to a public report.
We have not independently run these sites in Servo. The release evidence supports steady progress, not a blanket replacement recommendation for every browser workload. Our diagram models an acceptance check so readers can decide what compatibility means for their own task.
September 8: update to Servo 0.5, distinguish earlier working pages from new fixes, and separate visible text selection from interactive selection.