Comments (6)
@Akxe I think they just need to redo implementation of cdk overlay how it works and modals. Other stuff should be fine because it's uses cdk overlays.
Indeed, but it means that every API that is using overlay is affected and without workaround
from components.
Yeah we should be embracing web standards here.
from components.
@wagnermaciel I would argue that this issue is P3 or maybe above since there is no workaround...
- The dialog API has been stable since 2022, and it does affect all overlays. Meaning that all listed below are affected:
- Tooltip
- Overlay
- Select (menu)
- Autocomplete
- Datepicker
- Menu
- Sidenav
- SnackBar
- and maybe more
- There is no workaround. If something is using the underlying top layer API, it will always be on top
- The severity of this issue will grow in time as more libraries and extensions start using these APIs
from components.
@Akxe I think they just need to redo implementation of cdk overlay how it works and modals. Other stuff should be fine because it's uses cdk overlays.
from components.
I say the are not compatible, not completely. For example popover/dialog or more fundamental overlay api has layers, which does not exist on popover api and what’s more will not be implemented. One way could be to move main container of overlay api to top layer to keep existing layer behavior but also keep eveything in one top layer. But then we go into anchor size/position etc… so Ii would rather have new api to work with native popover, and leave css where css is due. Also now that we can create top layer elements from anywhere in dom we don’t need to keep container element and fight with passing data to dialog through injector , have close on router navigation etc.. all that can be done more easily now that dialog/popover can just use native host injectors - of course does not need to, we can still have more similar api to todays one that provide ability to create router independent dialogs. But now we can for example just create those dialogs/popover elements inside root node,not outside it etc. Mayby those two apis should be separate even
from components.
I say the are not compatible, not completely. For example popover/dialog or more fundamental overlay api has layers, which does not exist on popover api and what’s more will not be implemented.
Do you have an example of component using this behaviour? I am not sure I know of any
The řešit is well thought, well done 😊
from components.
Related Issues (20)
- bug(mat-icon-button): anchor is pointing to the incorrect template
- bug(MatFormField): Cannot change color of MatFormField TextArea with CSS HOT 5
- feat(google-maps): Dynamic update support for advanced marker options HOT 1
- bug(cdk-drag): scroll doesn't work if scroll container is inside cdkDropList element HOT 1
- Getting NG0956 when presenting mat-calendar in a cdkConnectedOverlay HOT 1
- bug(material/core): ripple element not destroyed after trigger change
- bug(mat-button): Ripple effect missing when using encapsulation: ShadowDom HOT 1
- bug(mat-button-icon): m3 mat-icon-button is not applying color HOT 6
- [disabled] attribute not working in mat-select formfields after upgrading to Angular 15 HOT 4
- bug(mat-select): won't collapse on IOS with a full access keyboard
- bug(CdkPortal): Change detection loop when component portal uses NgModel HOT 3
- Release builds are unable to build using workers
- feat(cdk/scrolling): Wish virtual scrolling would support dynamic item heights HOT 1
- bug(COMPONENT): ThemePalette for Material 3 HOT 2
- docs-feat(tabs): Include example/mention of setting mat-align-tabs dynamically
- bug(Angular Youtube player: Getting YT is undefined in Pause video function HOT 4
- Drag&Drop wrap strange behavior
- bug(@angular/google-maps): (zoomChanged) Observable returns undefined
- bug(Selector/option): Option status inside a selector not read when "selected"
- bug(menu)[matMenuTriggerFor]: Trigger does not update ARIA values correctly in OnPush components (Accessibility) HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from components.