Web Components

Developers can create custom, reusable, encapsulated HTML tags for the web using Web Components. Components use the Custom Element standard, frequently in combination with the Shadow DOM, HTML Templates, and ES Modules.

Describe the bug
In the config.js addParameters function, if I set isFullscreen: true and open the webpage, it is fullscreen on startup. But if I set isFullscreen: false and open the webpage again, it is still full-screen on startup.

To Reproduce

Set isFullscreen: true, open the webpage,
Close the webpage or stop the server
Set isFullscreen: false, open the webpa

Description

Polymer.PropertiesMixin fails to create property accessors in IE11 for certain important names like disabled.

Live Demo

https://github.com/bashmish/bug-ie11-polymer-properties-mixin

Steps to Reproduce

Open tests and see what is failing in IE11 comparing to other browsers.

Expected Results

disabled has corresponding accessors that allow to react to ch

Running gatsby build gives the following error:

error Building static HTML failed
  15 |  * True if the custom elements polyfill is in use.
  16 |  */
> 17 | export const isCEPolyfill = window.customElements !== undefined &&
     |        ^
  18 |     window.customElements.polyfillWrapFlushCallback !==
  19 |         undefined;
  20 | /**


  WebpackError: ReferenceError: windo

I'm looking to write preact or vanilla web components and ssr prerender them into pages. When looking at your SSR example I see that you're using skates custom Element class to extend from. Could we get some docs on this class? Could we get an example of ssr using preact?

TestCafe runs on Windows, MacOS, and Linux. It supports multiple desktop (Chrome, Firefox, IE11, Edge, Safari), mobile, remote and cloud browsers (UI or headless). TestCafe is free to use under the MIT license.

https://devexpress.github.io/testcafe/
https://github.com/devexpress/testcafe

It's important, I think, if the goal is to communicate that this can replace React in more ways than function.

The following warnings appear in the console during compilation, and they are also shown by stylable intelligence:

WARNING in Stylable: "@st-scope" must receive a simple selector, but instead got: ":global(.foo)"
@st-scope :global(.foo) { }

WARNING in Stylable: "@st-scope" received an unknown symbol: "html"
@st-scope html { }

The compiled CSS works correctly, though.

Describe the bug; what happened?
The select menu shows up behind other controls.

What are the steps to reproduce the issue?
Compose a page by vertically placing . The select's menu shows up behind the compone

<head> section of the HTML documents on the open-ui.org website lacks <title> element.

Even while seo.js component has a title={title} in it,
for some reason it does not get rendered to the HTML output.

        return (
          <Helme

I'm submitting a ...
[ ] bug report
[ X] feature request
[ ] support request

Current behavior:
Splash screen not showing on iOS

Expected behavior:
Splash screen is showing on iOS, and can be generated through ionic resources

Steps to reproduce:
Launch the application on an iPhone and expect to see a splash screen

Related code:

According to [this article]

Based off of conversation in #353, it might be worth adding a simple example of a loader component in the dimmer docs:

<sui-dimmer class="inverted" [isDimmed]="isLoading" [isClickable]="false" [transitionDuration]="200">
    <div class="ui text loader">Loading</div>
</sui-dimmer>

Currently the module field on package.json points to src/simpla.js but really it should point to a separate build, that's been transpiled, but not bundled. This means that whatever module bundling system consumers are using will still be used, but it won't need to be transpiled. As it currently stands, users can come up against [this bug](https://github.com/facebookincubator/create-react-app

Child of #186

Create a list of short code snippets for a new docs page, to be placed under TS docs.

event listeners
querySelector
dataProvider

Some examples:

`@query` decorator

👎 using any:

@query('#grid')
private grid: any;

👍 using types:

@query('#grid')
private grid!

Proposal: Expose events when the user clicks on agenda events or manipulates tasks.

Description

If the user clicks on an agenda event, we should expose an event to the developer.

Similarly if a user adds a task, removes a task, edits a task, changes the state of a task, etc... we should expose these events

May	JUN	Jul
	12
2019	2020	2021

Web Components

Here are 1,191 public repositories matching this topic...

storybookjs / storybook

Polymer / polymer

Description

Live Demo

Steps to Reproduce

Expected Results

Tencent / omi

wiredjs / wired-elements

skatejs / skatejs

andreasbm / web-skills

github / time-elements

matthewp / haunted

karol-f / vue-custom-element

Polymer / polymer-bundler

wix / stylable

tbranyen / diffhtml

microsoft / fast-dna

WICG / open-ui

SAP / ui5-webcomponents

ionic-team / ionic-pwa-toolkit

edcarroll / ng2-semantic-ui

Polymer / web-component-tester

simplajs / simpla

Polymer / polymer-cli

github / details-dialog-element

rstacruz / remount

mappmechanic / awesome-stenciljs

elix / elix

github / details-menu-element

vaadin / vaadin-core

@query decorator

atomicojs / atomico

microsoftgraph / microsoft-graph-toolkit

Proposal: Expose events when the user clicks on agenda events or manipulates tasks.

Description

vaadin / vaadin

shprink / web-components-todo

Related Topics

`@query` decorator