feat: switch to CDK BreakpointsObserver
See original GitHub issueWe need to migrate to the CDK’s layout engine. This means the following:
- ~Switch to using
BreakpointsObserver
inMediaMonitor
~ - Deprecate
ObservableMedia
/MediaService
- Deprecate
MatchMedia
- Add server wrapper for
BreakpointsObserver
andMediaMatcher
- Update the CDK layout engine as necessary
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:9 (3 by maintainers)
Top Results From Across the Web
How to Manage Breakpoints using BreakpointObserver in ...
Before creating the breakpoints, let's add the Angular Material components, which will install the Angular CDK library under the hood. ng add @ ......
Read more >How To Detect Breakpoints Using the Angular CDK
Learn how to detect viewport size changes or matches against media queries using the BreakpointObserver and MediaMatcher services from the ...
Read more >Angular CDK's BreakpointObserver. tldr; | by Preston Lamb
The Angular CDK's LayoutModule has a BreakpointObserver class that you can inject into a component, provide a breakpoint (or breakpoints) ...
Read more >KanokGB (@kanokgb) / Twitter
Turn on account notifications to keep up with all new content. ... How to detect viewport size with the help of #Angular cdk...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@angular/cdk
BreakpointObserver will not replace@angular/flex-layout
MediaObserver. MediaObserver is an enhanced version that notifies subscribers of activations for standard AND overlapping (lt-xxx, gt-xxx) breakpoints.We are adding the following enhancements to @angular/flex-layout:
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.