mirror of
https://github.com/fluencelabs/wasm-bindgen
synced 2025-04-22 12:42:14 +00:00
3f4acc453b
* Pre-generating web-sys * Fixing build errors * Minor refactor for the unit tests * Changing to generate #[wasm_bindgen} annotations * Fixing code generation * Adding in main bin to wasm-bindgen-webidl * Fixing more problems * Adding in support for unstable APIs * Fixing bug with code generation * More code generation fixes * Improving the webidl program * Removing unnecessary cfg from the generated code * Splitting doc comments onto separate lines * Improving the generation for unstable features * Adding in support for string values in enums * Now runs rustfmt on the mod.rs file * Fixing codegen for constructors * Fixing webidl-tests * Fixing build errors * Another fix for build errors * Renaming typescript_name to typescript_type * Adding in docs for typescript_type * Adding in CI script to verify that web-sys is up to date * Fixing CI script * Fixing CI script * Don't suppress git diff output * Remove duplicate definitions of `Location` Looks to be a preexisting bug in wasm-bindgen? * Regenerate webidl * Try to get the git diff command right * Handle named constructors in WebIDL * Remove stray rustfmt.toml * Add back NamedConstructorBar definition in tests * Run stable rustfmt over everything * Don't run Cargo in a build script Instead refactor things so webidl-tests can use the Rust-code-generation as a library in a build script. Also fixes `cargo fmt` in the repository. * Fixup generated code * Running web-sys checks on stable * Improving the code generation a little * Running rustfmt Co-authored-by: Alex Crichton <alex@alexcrichton.com>
33 lines
1.1 KiB
Rust
33 lines
1.1 KiB
Rust
//! Raw API bindings for Web APIs
|
|
//!
|
|
//! This is a procedurally generated crate from browser WebIDL which provides a
|
|
//! binding to all APIs that browser provide on the web.
|
|
//!
|
|
//! This crate by default contains very little when compiled as almost all of
|
|
//! its exposed APIs are gated by Cargo features. The exhaustive list of
|
|
//! features can be found in `crates/web-sys/Cargo.toml`, but the rule of thumb
|
|
//! for `web-sys` is that each type has its own cargo feature (named after the
|
|
//! type). Using an API requires enabling the features for all types used in the
|
|
//! API, and APIs should mention in the documentation what features they
|
|
//! require.
|
|
|
|
#![doc(html_root_url = "https://docs.rs/web-sys/0.2")]
|
|
#![allow(deprecated)]
|
|
|
|
mod features;
|
|
pub use features::*;
|
|
|
|
/// Getter for the `Window` object
|
|
///
|
|
/// [MDN Documentation]
|
|
///
|
|
/// *This API requires the following crate features to be activated: `Window`*
|
|
///
|
|
/// [MDN Documentation]: https://developer.mozilla.org/en-US/docs/Web/API/Window
|
|
#[cfg(feature = "Window")]
|
|
pub fn window() -> Option<Window> {
|
|
use wasm_bindgen::JsCast;
|
|
|
|
js_sys::global().dyn_into::<Window>().ok()
|
|
}
|