Web: use the word "Web" correctly and consistently (#3785)

src/platform_impl/web/event_loop/mod.rs

@@ -5,7 +5,7 @@ use crate::application::ApplicationHandler;
 use crate::error::EventLoopError;
 use crate::event::Event;
 use crate::event_loop::ActiveEventLoop as RootActiveEventLoop;
-use crate::platform::web::{ActiveEventLoopExtWebSys, PollStrategy, WaitUntilStrategy};
+use crate::platform::web::{ActiveEventLoopExtWeb, PollStrategy, WaitUntilStrategy};
 
 mod proxy;
 pub(crate) mod runner;

src/platform_impl/web/event_loop/runner.rs

@@ -439,7 +439,7 @@ impl Shared {
     }
 
     pub fn init(&self) {
-        // NB: For consistency all platforms must call `can_create_surfaces` even though web
+        // NB: For consistency all platforms must call `can_create_surfaces` even though Web
         // applications don't themselves have a formal surface destroy/create lifecycle.
         self.run_until_cleared(
             [Event::NewEvents(StartCause::Init), Event::CreateSurfaces].into_iter(),
@@ -604,7 +604,7 @@ impl Shared {
         self.exit();
         self.apply_control_flow();
         // We don't call `handle_loop_destroyed` here because we don't need to
-        // perform cleanup when the web browser is going to destroy the page.
+        // perform cleanup when the Web browser is going to destroy the page.
         self.handle_event(Event::LoopExiting);
     }
 

src/platform_impl/web/mod.rs

@@ -1,14 +1,14 @@
-// Brief introduction to the internals of the web backend:
-// The web backend used to support both wasm-bindgen and stdweb as methods of binding to the
-// environment. Because they are both supporting the same underlying APIs, the actual web bindings
+// Brief introduction to the internals of the Web backend:
+// The Web backend used to support both wasm-bindgen and stdweb as methods of binding to the
+// environment. Because they are both supporting the same underlying APIs, the actual Web bindings
 // are cordoned off into backend abstractions, which present the thinnest unifying layer possible.
 //
 // When adding support for new events or interactions with the browser, first consult trusted
 // documentation (such as MDN) to ensure it is well-standardised and supported across many browsers.
-// Once you have decided on the relevant web APIs, add support to both backends.
+// Once you have decided on the relevant Web APIs, add support to both backends.
 //
 // The backend is used by the rest of the module to implement Winit's business logic, which forms
-// the rest of the code. 'device', 'error', 'monitor', and 'window' define web-specific structures
+// the rest of the code. 'device', 'error', 'monitor', and 'window' define Web-specific structures
 // for winit's cross-platform structures. They are all relatively simple translations.
 //
 // The event_loop module handles listening for and processing events. 'Proxy' implements

src/platform_impl/web/window.rs

@@ -325,7 +325,7 @@ impl Inner {
 
     #[inline]
     pub fn set_ime_cursor_area(&self, _position: Position, _size: Size) {
-        // Currently a no-op as it does not seem there is good support for this on web
+        // Currently not implemented
     }
 
     #[inline]