Known bugs

Where to look

Live lists of open defects, regressions, and feature gaps are kept on the GitHub project for AWeb 3.6 maintained by amigazen project:

• Repository and readme: https://github.com/amigazen/aweb3/
• Issues (searchable list): https://github.com/amigazen/aweb3/issues

Visit these URLs using a modern web browser on a system that can reach GitHub.

GitHub and modern browsers

The GitHub website itself assumes a modern HTML5/CSS3/JavaScript browser. AWeb is not able to render GitHub usefully: you will need a current desktop or mobile browser to read issues, pull requests, and project documentation on GitHub.

What AWeb does not support (needed for GitHub, Google, and similar sites)

Sites like GitHub or Google assume a current engine. AWeb does not implement the following (non-exhaustive); absence of these is why most "modern" pages fail before any AWeb-specific bug matters:

• HTML5 document model and elements (e.g. video, audio, canvas, svg as first-class document graphics, template, slot, semantic layout tags as live components)
• CSS3 and later (e.g. Flexbox, Grid, multi-column, advanced selectors, @media queries as authors use them today, custom properties / variables, animations and transitions as on mainstream sites)
• ECMAScript 2015+ (ES6 and later: modules import/export, class, async/await, native Promise stacks, arrow functions, Map/Set used pervasively, tagged templates, etc.)
• Large single-page-app stacks (React, Vue, Angular, Svelte bundles and similar transpiled/minified site shells)
• fetch() and other modern network APIs (AWeb targets JavaScript 1.5 / ES3 plus experimental XMLHttpRequest, not the modern fetch ecosystem)
• Web Workers, SharedWorker, Service Worker and offline / installable PWA behaviour
• WebSocket, WebRTC, HTTP/2, HTTP/3 / QUIC
• WebAssembly (wasm) runtimes
• WebGL and GPU-backed in-browser graphics APIs
• Shadow DOM and Custom Elements (Web Components)
• Rich DOM Level 3+ APIs (querySelector/querySelectorAll, classList, mutation observers, full event model as on desktop Chrome, drag-and-drop API, intersection observers, etc. — many are missing or incomplete)
• localStorage / sessionStorage, IndexedDB, and large client-side storage models sites rely on
• Content Security Policy, Subresource Integrity, and other modern security headers interpreted the way current browsers do
• Embedded OAuth/OpenID Connect and social-login flows driven by heavy cross-origin script (as used on GitHub and Google accounts)
• In-page PDF, EPUB, or other viewers delivered as web apps
• Ubiquitous Unicode and complex-script shaping as on a 2020s desktop browser (AWeb has selective UTF-8 and optional TTEngine paths, not full universal coverage)
• Continuous TLS feature churn (cipher suites, ALPN expectations, pinned behaviours) beyond what AmiSSL and this tree are tested for on live sites

For release-specific notes and a high-level change log shipped with this binary, see Release history in this documentation set.