LGTM1 as an IWA API.

On Wed, Feb 11, 2026 at 4:24 PM Chromestatus <
[email protected]> wrote:

> *Contact emails*
> [email protected], [email protected]
>
> *Explainer*
> https://github.com/WICG/web-printing
>
> *Specification*
> https://wicg.github.io/web-printing
>
> *Summary*
> Enables deeper integration with printer-related functionality in Isolated
> Web Apps. This API is targeted at Isolated Web Apps only and it's following
> the https://www.chromium.org/blink/launching-features/isolated-web-apps/
> process. This API provides a set of JavaScript methods that allow
> developers to query local printers, submit print jobs to the most
> appropriate printers, and manage print job options and status. To represent
> these concepts, it relies on the attribute names and semantics from the
> Internet Printing Protocol (IPP) specifications.
>
> *Blink component*
> Blink
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%22>


Perhaps we should create a component for all IWA APIs or something? We
regularly triage <https://www.chromium.org/blink/blink-triaging/> bugs out
of the top-level Blink component so it's not a permanent home for any bugs.


> *Web Feature ID*
> *No information provided*
>
> *Motivation*
> The Web Printing API strives to improve the general printing experience
> with a primary focus on remote/virtual desktop systems by providing a
> seamless way for remote clients to interact with printers directly in
> Isolated Web Apps. The proposed API methods unlock proper printer
> forwarding by allowing the remote client to access essential information
> about printers on the near side. This eliminates the need for tedious
> manual configuration, such as setting up virtual printers, and excessive
> user interactions such as having to click through print job settings twice
> (once on the remote side & once locally). It also enables remote document
> rendering to be tailored to the capabilities of the local printer.
>
> *Initial public proposal*
> https://github.com/WICG/proposals/issues/120
>
> *TAG review*
> https://github.com/w3ctag/design-reviews/issues/910
>
> *TAG review status*
> Pending
>
> *Risks*
>
>
> *Interoperability and Compatibility*
> Other browser may choose to implement this API.
>
> *Gecko*: No signal
>
> *WebKit*: No signal
>
> *Web developers*: Positive (
> https://github.com/WICG/proposals/issues/120#issuecomment-1752979770) Positive
> feedback from Citrix.
>
> *Other signals*:
>
> *WebView application risks*
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
> *No information provided*
>
>
> *Debuggability*
> *No information provided*
>
> *Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, ChromeOS, Android, and Android WebView)?*
> No
>
> *Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
> No
> Web Platform Tests are planned for the cross-platform launch. Creating Web
> Platform Tests will be complicated because this API connects to physical
> devices and this would require extensions to BiDi driver API.
>
> *Flag name on about://flags*
> enable-printing-web-api
>
> *Finch feature name*
> WebPrinting
>
> *Rollout plan*
> Will ship enabled for all users
>
> *Requires code in //chrome?*
> True
>
> *Tracking bug*
> https://b.corp.google.com/issues/302505962
>
> *Launch bug*
> https://launch.corp.google.com/launch/4427089
>
> *Estimated milestones*
> Shipping on desktop 147
>
> *Anticipated spec changes*
>
> Open questions about a feature may be a source of future web compat or
> interop issues. Please list open issues (e.g. links to known github issues
> in the project for the feature specification) whose resolution may
> introduce web compat/interop risk (e.g., changing to naming or structure of
> the API in a non-backward-compatible way).
> *No information provided*
>
> *Link to entry on the Chrome Platform Status*
> https://chromestatus.com/feature/5100352332627968?gate=5186894732460032
>
> *Links to previous Intent discussions*
> Intent to Prototype:
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZWnOqSBA6cxpngy5cutJz9051RLAGgHzmHMijwvDuRTvD0Mw%40mail.gmail.com
>
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/698cf37f.710a0220.13b4f7.050d.GAE%40google.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/698cf37f.710a0220.13b4f7.050d.GAE%40google.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9YoxgdDpAoHYCyLwJSuxG32D_jiR02_pg%2BKMBbbMpqVg%40mail.gmail.com.

Reply via email to