ember-element-query 
- Use element queries effortlessly on any element or component.
- Use it in the form of the
{{element-query}}modifier or the<ElementQuery as |EQ|>component. - Apply styles that respond based on element's own width rather than viewport width.
- Do CSS transforations and template transformations.
Element queries are a technique to do responsive transformations based on element's own size rather than viewport size.
It lets you implement reusable responsive components — with encapsulated styles, decoupled from their parent context. Such components will realign their content depending on how much space is available to them.
For example, if you put a responsive component into a tight sidebar, it will align its content vertically. When the sidebar expands, the component will realign horizontally in order to efficiently use available space.
Here's a biased comparison table with competing addons (as of 2021.08):
| | ember-element-query | ember-fill-up | ember-container-query | | -------------------------------------------------- | :-----------------: | :--------------------------------------------------------: | :-----------------------------------------------------------------------: | | Octane | ✔ | 🚫 | ✔ | | ResizeObserver | ✔ | ✔ | 🚫 | | Offers a modifier | ✔ | 🚫 | 🚫 | | Offers a component | ✔ | ✔ | ✔ | | Actively maintained | ✔ | 🚫 | ✔ | | API convenience | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ |
See detailed comparison with code samples.
- Using attributes in CSS - Edge cases - ⚠ Use in compound selectors only! - As a modifier - As a component - onResize callback - Custom sizes - Using height - Using aspect ratio - Opting out of width attributes - Customizing attribute prefix - Using multiple modifiers on the same element - Disabling - Customizing component element - Debouncing - CSS fallback - FastBoot fallback - Comparison
- [Defining custom rules rules, using template and CSS transformations](#defining-custom-rules-rules-using-template-and-css-transformations)
- [Using default rule definitions](#using-default-rule-definitions)
- [Customizing element tag while doing template transformations](#customizing-element-tag-while-doing-template-transformations)
- [Customizing element tag while doing pure CSS transformations](#customizing-element-tag-while-doing-pure-css-transformations)
- [Using directly on images and other void elements](#using-directly-on-images-and-other-void-elements)
- [Using both width and height in a rule for template transformation](#using-both-width-and-height-in-a-rule-for-template-transformation)Demo
https://lolmaus.github.io/ember-element-query/This addon's demo is borrowed from ember-container-query per @ijlee2's generous permission.
API Docs
https://lolmaus.github.io/ember-element-query/api/Roadmap
This addon is- x
{{element-query}}modifier
ResizeObserver
x Calls the onResize callback with params
x Applies attributes to elements
x Accepts sizes
x Accepts sizesHeight
x Accepts sizesRatio
x Accepts prefix
x Updates on arugments change
x Add fool-proof exceptions
x Disabling
x Applying a general [eq] attribute - x
<ElementQuery>component
onResize callback with params
x Yields block params
x Accepts sizes
x Accepts sizesHeight
x Accepts sizesRatio
x Accepts prefix
x Accepts tagName
x Disabling
x Concept
x Feature description
x Usage
x Browser support
x Comparison with alternatives
x TypeDoc API documentation* [x] Document
* [x] Set up auto deployment- x Demo app
Rationale
CSS media queries have a few disadvantages:- They account for scrollbar width. On OSes with a scrollbar such as Windows and Linux, available document width is some 15px smaller than the one detected by a media query. Resulting styles are slightly inconsistent across OSes.
- They are designed for creating responsive layouts, whereas making responsive components is unreasonably hard:
All those problems wouldn't exist if we were able to apply styles conditionally based on element's own width:
/* Hypothetical sample. I wish these were possible, but alas! */
/* When .my-menu is <= 499px, apply margin-bottom to .my-menu--item */
.my-menu:max-width(499px) .my-menu--item {
margin-bottom: 10px;
}
/* When .my-menu is >= 500px, apply flex to it */
.my-menu:min-width(500px) {
display: flex;
}
/* When .my-menu is >= 500px, apply margin-right to .my-menu--item */
.my-menu:min-width(500px) .my-menu--item {
margin-right: 10px;
}Unfortunately, CSS is not aware of element's current width, so pseudoselectors like
:min-width(500px) are impossible... unless you use a tool like ember-element-query.Concept of sizes
ember-element-query operates with sizes. "Sizes" are like T-shirt sizes, except they indicate element width.The default sizes scale is:
Breakpoints: 0 200px 400px 600px 800px 1000px 1200px 1400px
├─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────>
Sizes: · xxs · xs · s · m · l · xl · xxl · xxxl For example, an element is considered to be of size
m when its width is >= 600px and < 800px.Here's an explicit sizes chart:
Breakpoints: 0 200px 400px 600px 800px 1000px 1200px 1400px
├─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────┼─────────>
Sizes: · xxs · xs · s · m · l · xl · xxl · xxxl
· · · · · · · ·
xxs │ · · · · · · ·
0—199 ├────────┤· · · · · · ·
· · · · · · · ·
xs ├─────────┤ · · · · · ·
200—399 ├──────────────────┤· · · · · ·
· · · · · · · ·
s ├───────────────────┤ · · · · ·
400—599 ├────────────────────────────┤· · · · ·
· · · · · · · ·
m ├─────────────────────────────┤ · · · ·
600—799 ├──────────────────────────────────────┤· · · ·
· · · · · · · ·
l ├───────────────────────────────────────┤ · · ·
800—999 ├────────────────────────────────────────────────┤· · ·
· · · · · · · ·
xl ├─────────────────────────────────────────────────┤ · ·
1000—1199 ├──────────────────────────────────────────────────────────┤· ·
· · · · · · · ·
xxl ├───────────────────────────────────────────────────────────┤ ·
1200—1399 ├────────────────────────────────────────────────────────────────────┤·
· · · · · · · ·
xxxl ├─────────────────────────────────────────────────────────────────────┤
1400+ ├──────────────────────────────────────────────────────────────────────────>How ember-element-query works
ember-element-query applies HTML attributes to an element indicating its current size.There are three types of attributes, all of them are applied at once:
at-<size>attribute is applied with element's current size.
For example, an element with width of `764px` will receive an `at-m` attribute.from-<size>attributes are applied with element's current size and all smaller sizes.
For example, an element with width of `764px` will receive attributes `from-xxs`, `from-xs`, `from-s` and `from-m`.to-<size>attributes are applied with element's current size and all larger sizes.
For example, an element with width of `764px` will receive attributes `to-m`, `to-l`, `to-xxl` and `to-xxxl`.- When you want say "when my element is of size M", use the
at-mattribute. - When you want say "when my element is of size M or larger", use the
from-mattribute. - When you want say "when my element is of size M or small", use the
to-mattribute.
Using attributes in CSS
In order to do responsive CSS transformations, use attributes like this:.foo[at-xxs] {
/* These styles when be applied when the element has exactly the size of `xxs`, namely 0—199 px. */
}
.foo[from-xs] {
/* These styles when be applied when the element has the size of `xxs` or larger, namely 200+ px. */
}
.foo[to-xl] {
/* These styles when be applied when the element has the size of `xl` or smaller, namely 0—1199 px. */
}
.foo[from-s][to-l] {
/* These styles when be applied when the element has the size between `s` and `l` inclusively, namely 400—999 px. */
}Responsive template transformations are also possible, see below.
Edge cases
Note that some attribute usages don't make much sense:- The smallest
from-and the largestto-attribute are applied at all times, thus.foo[from-xxs]and.foo[to-xxxl]selectors are both equivalent to simply.foo. .foo[to-xxs]is equivalent to.foo[at-xxs], and.foo[from-xxxl]is equivalent to.foo[at-xxxl]..foo[from-m][to-m]is equivalent to.foo[at-m].
⚠ Use in compound selectors only!
Attribute selectors in CSS should only be used in conjunction with semantic selectors.The following usage will mess up you website/app:
/* Never do this! */
[at-m] {
float: left;
}
/* Still quite bad */
aside[at-m] {
float: left;
}
/* OK */
.my-side-block[at-m] {
float: left;
}Installation
Useember-cli to install the addon as usual:ember i ember-element-querynpm i -D ember-element-queryyarn add -D ember-element-queryUsage
As a modifier
Using the modifier is preferred if you only do CSS transformations, which is recommended according to the Responsiv Web Design doctrine.Simply apply the
{{element-query}} modifier to any element or angle bracket component like this:<img {{element-query}}>As a result, element query attributes will be applied to the element. The result could look like this:
<img at-m from-xxs from-xs from-s from-m to-m to-l to-xl to-xxl to-xxxl>As a component
The component is useful when you need to do template transformations.If you want to render chunks of template conditionally, use this syntax:
<ElementQuery as |EQ|>
{{#if EQ.at-m}}
{{! This will only be rendered when the `<ElementQuery>` component is of size `m`. }}
{{/if}}
{{#if EQ.from-m}}
{{! This will only be rendered when the `<ElementQuery>` component is of size `m` or larger. }}
</EQ.from-m>
{{#if EQ.to-m}}
{{! This will only be rendered when the `<ElementQuery>` component is of size `m` or smaller. }}
{{/EQ.to-m}}
{{#if (and EQ.from-s EQ.to-l)}}
{{! This will only be rendered when the `<ElementQuery>` component is of size `s`, `m` or `l`. }}
{{/if}}
</ElementQuery>The first yield argument
EQ is an object with current element query attributes. Keys are attribute names and values are true. Non-matching attributes are undefined. Thus, {{#if EQ.from-m}} renders only when the element is of size m or larger.The second argument
EQInfo is the same object that is passed to the onResize callback described below.Advanced usage
onResize callback
You can pass a callback to theonResize argument and it will be called whenever the element resizes:@action
reportResize(eqInfo) {
eqInfo.element // => current element
eqInfo.width // => current element's width in px (number)
eqInfo.height // => current element's height in px (number)
eqInfo.ratio // => current element's aspect ratio (width/height, number)
eqInfo.size // => current element's width size name (string or undefined)
eqInfo.sizeHeight // => current element's height size name (string or undefined)
eqInfo.sizeRatio // => current element's aspect ratio size name (string or undefined)
eqInfo.prefix // => current prefix (string or undefined)
eqInfo.attributes // => matching element query attributes in array form: ['from-xxs', 'from-xs', ...]
eqInfo.attributesRecord // => matching element query attributes in object form: {'from-xxs': true, 'from-xs': true, ...}
// non-matching attributes are not defined on the object
}<img {{element-query onResize=this.reportResize}}><ElementQuery @onResize={{this.reportResize}}></ElementQuery>Custom sizes
Your tailored visual designs might require component switching layouts at specific breakpoints, different from this addon's defaults.You can override the defaults with the
sizes argument. It receives a plain object where keys are breakpoint names and arguments are numbers representing width.⚠ One of the numbers must be 0, otherwise the addon will crash your app.
<img
{{element-query
sizes=(hash
small=0
medium=350
large=700
)
}}
><ElementQuery
@sizes={{hash
small=0
medium=350
large=700
}}
>
</ElementQuery>The above example defines sizes like this:
small: 0—349 px,medium: 350—699 px,large: 700+ px.
When the element has the width of
421px, it will receive attributes at-medium, from-medium, to-medium, from-small and to-large. (Confused? See above.)Using height
By default, only attributes for horizontal sizes are applied to your element.If you want to use attributes for vertical sizes, set
sizesHeight to true:<img {{element-query sizesHeight=true}}><ElementQuery @sizesHeight={{true}}></ElementQuery>Enabling
heightSizes will cause two sets of attributes to be applied: width and height. Attributes representing width sizes will be the same as usual. Attributes representing height sizes will be postfixed with -height: xxs-height, xl-height, etc.This lets you apply CSS like this:
.foo[to-s][from-xl-height] {
/* I am thin and tall */
}You can customize height sizes by passing a hash to
@sizesHeight. Make sure that height size names are different from width sizes!<div
{{element-query
sizesHeight=(hash small-height=0 medium-height=200 large-height=400)
}}
>
</div><ElementQuery
@sizesHeight={{hash small-height=0 medium-height=200 large-height=400}}
as |EQ|
>
{{#if (and EQ.to-small-width EQ.from-large-height)}}
I am thin and tall.
{{/if}}
</ElementQuery>Of course, you can customize both
sizes and sizesHeight at the same time if you need.Using aspect ratio
By default, only attributes for horizontal sizes are applied to your element.If you want to use attributes for aspect ratio sizes, set
sizesRatio to true:<img {{element-query sizesRatio=true}}><ElementQuery @sizesRatio={{true}}></ElementQuery>By default, the following definition of aspect ratio sizes is used:
{
'very-tall': 0,
'tall': 0.5,
'squarish': 0.8,
'wide': 1.2,
'very-wide': 1.5,
}Note that while width and height use whole number of CSS pixels, ratios use fractions. For example, an element with the size of
1920×1080 will have an aspect ratio of 1.777..., which correpsonds to the very-wide ratio size.You can customize ratio sizes by passing a hash to
@sizesRatio. Make sure that aspect ratio size names are different from width and height sizes!<div
{{element-query
sizesRatio=(hash horizontal=0 square=1 vertical=1.0001)
}}
>
</div><ElementQuery
@sizesRatio={{hash horizontal=0 square=1 vertical=1.0001}}
as |EQ|
>
{{#if (EQ.at-square)}}
I am precisely* square.
{{/if}}
</ElementQuery>\ Mind that comparison of fractional numbers is not absolutely accurate in JavaScript. Aspect ratio sizes are supposed to represent ranges of aspect ratios, not individual aspect ratios. Aiming at a specicific aspect ratio (like in example above) may be inconsistent.
Opting out of width attributes
By default, default width attributes are applied to your element unless thesizes is overridden.If you want no width attributes to be applied, pass a falsy value into
sizes.Using height without width:
<img {{element-query sizes=false sizesHeight=true}}><ElementQuery @sizes=null @sizesHeight=true></ElementQuery>Using no attributes at all:
<img {{element-query sizes=null}}><ElementQuery @sizes=false></ElementQuery>The above will make it impossible to apply CSS or HTML transformations based on sizes. But the following features will still work:
- The
onResizecallback will be called with an object containing current width, height and aspect ratio of the element. - The
<ElementQuery>component will yield an object containing current width, height and aspect ratio of the element. - The
eqattribute will still be applied to the element. This hapens when the element query triggers for the first time.
Customizing attribute prefix
Use theprefix argument to adjust attribute prefix:<img {{element-query prefix="data-foo-"}}><ElementQuery @prefix="data-foo-"></ElementQuery>This will result in attributes like
data-foo-at-xl, data-foo-from-m, etc.Using multiple modifiers on the same element
One use case for this is to apply new styles based on new breakpoints without breaking (and refactoring) existing styles.You can use both width and height element queries on the same element like this:
<img
class="foo"
{{element-query}}
{{element-query sizes=(new-small=0 new-large=700)}}
>or
<img
class="foo"
{{element-query}}
{{element-query prefix="new-"}}
>⚠ The
{{element-query}} modifier adds and removes attributes aggressively and will interfere with other modifiers/libraries manipulating same attributes. It is your duty to ensure there is no conflict in attribute names. Adjust sizes, sizesHeight and prefix arguments to avoid conflicts.Disabling
Pass a truthy value intoisDisabled to disable element query functionality:<img
{{element-query isDisabled=true}}
><ElementQuery
@isDisabled={{true}}
>
</ElementQuery>⚠ This property is intended for debugging purposes or disabling element queries entirely. If you change
isDisabled to true dynamically, element query attributes will freeze in their current state. There is no cleanup.Customizing component element
The<ElementQuery> component accepts a @tagName argument that allows tweaking the component's root tag:<ElementQuery @tagName="img" src="https://i.imgur.com/iP9xl86.gif" alt="A handsome person"/>This wouuld result in the followingg HTML rendered (element query tags not shown):
<img src="https://i.imgur.com/iP9xl86.gif" alt="A handsome person">Debouncing
Use thedebounce argument to set a limit to how frequently attributes recalculate and the onResize callback is called while the window is being continuously resized.It accepts a number of milliseconds and defaults to
100. This means that the refresh will be happening at a rate of 10 times per second (1000 / 100 = 10).This example with refresh once per second:
<img
{{element-query debounce=1000}}
><ElementQuery
@debounce={{1000}}
>
</ElementQuery>This addon uses window.requestAnimationFrame. Even if you set
debounce to 0, the refresh rate will still be limited to either 60 or to the refresh rate of the screen.It is not recommended to use a low refresh rate due to possible perormance issues. For example, if you do this:
<img
{{element-query
@debounce=0
@onResize=this.updateSrc
}}
>@service cdn;
@action updateSrc({element, width, height}) {
element.src = this.cdn.getImageSrcForSize({width, height});
}...then playing with window size for several seconds will cause hundreds or thousands of
src updates to be queued, which would cause the image to flicker.CSS fallback
⚠ When navigating between routes, there may be a flash of unstyled content: a very short moment when the component is rendered, but its element queries are not applied yet. This happens becauseember-element-query addon needs the component to be rendered in order to measure its size, before responsive styles can be applied.Consider this SCSS. Here we have two layouts: horizontal and vertical.
.MyComponent {
// This layout will be applied when the element is known to be small.
&[to-m] {
// Vertical layout. Children should have margins between them.
> *:not(:last-child) {
margin-bottom: 20px;
}
}
// This layout is applied when the element is known to be large.
&[from-l] {
// Horizontal layout. Children should be positioned in a row.
margin-bottom: 20px;
}
}During the flash of unstyled content, neither layout is applied because
ember-element-query hasn't yet applied its attributes.This is suboptimal. Instead, you want one of the layouts to be the default one: applied when element query attributes are unavailable.
For this use case, when the element's size is first measured,
ember-element-query applies the eq attribute to the element and keeps it forever. Thus, the :not([eq]) selector matches the element only while element queries have not yet being applied.In order to make one of the layouts a default, add
:not([eq]) to its selectors:.MyComponent {
// This layout will be applied when the element is known to be small or when its size is unknown.
&:not([eq]), &[to-m] {
// Vertical layout. Children should have margins between them.
> *:not(:last-child) {
margin-bottom: 20px;
}
}
// This layout is applied when the element is known to be large.
&[from-l] {
// Horizontal layout. Children should be positioned in a row.
margin-bottom: 20px;
}
}This would remove the flash of unstyled content at least for some screen sizes.
FastBoot fallback
Unfortunately, FastBoot does not have information about user's screen size. When a user vistis a FastBoot-driven website, they initially see a page without anyember-element-query attributes. When FastBoot rehydrates, element queries kick in. As a result, page layout may suddenly change after the user has already started reading and scrolling, causing frustration.One workaround is to use ember-useragent. Its
isMobile, isTablet and isDesktop boolean properties let you apply some defaults. The result is very crude, heuristical — but that's better than nothing.Since reusable components can be used in different contexts, it is recommended that you apply the fallback on parent level.
Responsive component:
<div
class="my-component"
{{element-querysizes=(hash small=0 medium=350 large=700)}}
...attributes
>
</div>.my-component { /* */}
.my-component[from-medium] { /* */ }
.my-component[from-large] { /* */ }Parent:
<MyComponent
from-medium={{and this.fastboot.isFastBoot (or this.userAgent.device.isTablet this.userAgent.device.isDesktop)}}
from-large-={{and this.fastboot.isFastBoot this.userAgent.device.isDeskto)}}
/>Unfortunately, this requires the parent to know which attributes are used in component's CSS, since providing all possible attributes would be quite tedious, especially for default sizes, which are numerous.
Browser support
IE is not supported becauseember-element-query uses modern ECMAScript APIs.ember-element-query is based on the ResizeObserver which is also not supported by IE.As of 2020-06,
ResizeObserver supports the following major browsers:- Chrome: 64+ (since 2018-01-23),
- Firefox: 69+ (since 2019-09-02, desktop only),
- Safari: 13.1+ desktop, 13.4+ iOS (since 2020-03-24).
See caniuse.com for detailed stats.
⚠ Note that old iOS devices do not have
ResizeObserver support, so you might want to use a polyfill. iOS Safari is the new IE. 😬Alternatives
There are a few other Ember addons implementing element queries, such as:- https://github.com/chadian/ember-fill-up/
- https://github.com/ijlee2/ember-container-query
ember-element-query was implemented to offer a simpler API at the cost of being opinionated.Other addons are full-fledged element query addons that aren't as much opinionated. Their approach is defining rules on element query components. For example, if you want your component to respond to
0—350px, 350px+, 350px—699px and 700px+ — you will need to define four rules on the component. An unexpected challenge is to come up with meaningful names for each range.Every time you need another rule, you need to add it on the component before you're able to use it in CSS.
With
ember-element-query, you only need to define breakpoints. The example above uses only two breakpoints: 350px and 700px — and all combinations of rules become available automatically via HTML attributes.💡
ember-fill-up and ember-container-query and ember-element-query are all full-featured element query addons. ember-element-query's goal is to provide a simpler API, making it more convenient to use. It encourages using pure CSS transformations, accoridng to the Responsive Web Design paradigm, though template transformations are also possible and convenient.Comparison
As of 2021.08.Defining custom rules rules, using template and CSS transformations
Given breakpoints 350, 700 and 1050:ember-fill-up:
```hbs
<FillUp
class="my-component"
@breakpoints={{hash
small=(fill-up-lt 350)
medium=(fill-up-between 350 700)
large=(fill-up-between 700 1050)
extraLarge=(fill-up-gte 1050)
mediumAndBigger=(fill-up-gte 350)
largeAndBigger=(fill-up-gte 700)
mediumAndSmaller=(fill-up-lt 700)
largeAndSmaller=(fill-up-lt 1050)
mediumToLarge=(fill-up-between 350 1050)
}}
as |F|
>
{{#if F.breakpoints.small}}...{{/if}}
{{#if F.breakpoints.medium}}...{{/if}}
{{#if F.breakpoints.large}}...{{/if}}
{{#if F.breakpoints.extraLarge}}...{{/if}}
{{#if F.breakpoints.mediumAndBigger}}...{{/if}}
{{#if F.breakpoints.largeAndBigger}}...{{/if}}
{{#if F.breakpoints.mediumAndSmaller}}...{{/if}}
{{#if F.breakpoints.largeAndSmaller}}...{{/if}}
{{#if F.breakpoints.mediumToLarge}}...{{/if}}
</FillUp>
```
```css
.my-component[fill-up-small] {}
.my-component[fill-up-medium] {}
.my-component[fill-up-large] {}
.my-component[fill-up-extraLarge] {}
.my-component[fill-up-mediumToLarge] {}
.my-component[fill-up-largeAndBigger] {}
.my-component[fill-up-mediumAndSmaller] {}
.my-component[fill-up-largeAndSmaller] {}
.my-component[fill-up-mediumToLarge] {}
```
👆 Note how you need to repeat same breakpoints several times in rule definitions. In order to avoid multiple sources of truth, you could wrap component invocation with `{{let}}`, but that increases the boilerplate.ember-container-query:
```hbs
<ContainerQuery
class="my-component"
@features={{hash
small=(cq-width max=349)
medium=(cq-width min=350 max=699)
large=(cq-width min=700 max=1049)
extraLarge=(cq-width min=1050)
mediumAndBigger=(cq-width min=350)
largeAndBigger=(cq-width min=700)
mediumAndSmaller=(cq-width max=699)
largeAndSmaller=(cq-width max=1049)
mediumToLarge=(cq-width min=350 max=1049)
}}
as |CQ|
>
{{#if CQ.features.small}}...{{/if}}
{{#if CQ.features.medium}}...{{/if}}
{{#if CQ.features.large}}...{{/if}}
{{#if CQ.features.extraLarge}}...{{/if}}
{{#if CQ.features.mediumAndBigger}}...{{/if}}
{{#if CQ.features.largeAndBigger}}...{{/if}}
{{#if CQ.features.mediumAndSmaller}}...{{/if}}
{{#if CQ.features.largeAndSmaller}}...{{/if}}
{{#if CQ.features.mediumToLarge}}...{{/if}}
</ContainerQuery>
```
```css
.my-component[data-container-query-small] {}
.my-component[data-container-query-medium] {}
.my-component[data-container-query-large] {}
.my-component[data-container-query-extraLarge] {}
.my-component[data-container-query-mediumAndBigger] {}
.my-component[data-container-query-largeAndBigger] {}
.my-component[data-container-query-mediumAndSmaller] {}
.my-component[data-container-query-largeAndSmaller] {}
.my-component[data-container-query-mediumToLarge] {}
```
👆 Note how you need to manually account for ±1 error in rule definitions.ember-element-query:
```hbs
<ElementQuery
class="my-component"
@sizes={{hash small=0 medium=350 large=700 extraLarge=1050}}
as |EQ|
>
{{#if EQ.at-small}}...{{/if}}
{{#if EQ.at-medium}}...{{/if}}
{{#if EQ.at-large}}...{{/if}}
{{#if EQ.at-extraLarge}}...{{/if}}
{{#if EQ.from-medium}}...{{/if}}
{{#if EQ.from-large}}...{{/if}}
{{#if EQ.to-medium}}...{{/if}}
{{#if EQ.to-large}}...{{/if}}
{{#if (and EQ.from-medium EQ.to-large)}}...{{/if}}
</ElementQuery>
```
```css
.my-component[at-small] {}
.my-component[at-medium] {}
.my-component[at-large] {}
.my-component[at-extraLarge] {}
.my-component[from-medium] {}
.my-component[from-large] {}
.my-component[to-medium] {}
.my-component[to-large] {}
.my-component[from-medium][to-large] {}
```Using default rule definitions
ember-fill-up:
Does not provide any defaults.ember-container-query:
Does not provide any defaults.ember-element-query:
Provides [reasonable defaults](#concept-of-sizes).
**Those defaults can be used as a common design language, and all components in your app can be using them, reducing the boilerplate to:**
```hbs
<ElementQuery></ElementQuery>
```
or
```hbs
<div {{element-query}}></div>
```Customizing element tag while doing template transformations
ember-fill-up:
Not supported. Responsive componetns are limited to `<div>`.ember-container-query:
Uses [ember-element-helper](https://github.com/tildeio/ember-element-helper) as a polyfill for [RFC 389](https://github.com/emberjs/rfcs/blob/master/text/0389-dynamic-tag-names.md) ([tracking](https://github.com/emberjs/rfc-tracking/issues/42)):
```hbs
<ContainerQuery @tagName="article">
</ContainerQuery>
```ember-element-query:
Uses [ember-element-helper](https://github.com/tildeio/ember-element-helper) as a polyfill for [RFC 389](https://github.com/emberjs/rfcs/blob/master/text/0389-dynamic-tag-names.md) ([tracking](https://github.com/emberjs/rfc-tracking/issues/42)):
```hbs
<ElementQuery @tagName="article">
</ElementQuery>
```Customizing element tag while doing pure CSS transformations
ember-fill-up:
Not supported. Responsive componetns are limited to `<div>`.ember-container-query:
Uses [ember-element-helper](https://github.com/tildeio/ember-element-helper) as a polyfill for [RFC 389](https://github.com/emberjs/rfcs/blob/master/text/0389-dynamic-tag-names.md) ([tracking](https://github.com/emberjs/rfc-tracking/issues/42)):
```hbs
<ContainerQuery @tagName="article">
</ContainerQuery>
```ember-element-query:
Naturally:
```hbs
<article {{element-query}}>
</article>
```Using directly on images and other void elements
ember-fill-up:
Not supported.
Workaround with two wrapper elements:
```hbs
<FillUp class="wrapper1" breakpoints=this.rules>
<div class=wrapper2>
<img class="image" src alt>
</div>
</FillUp>
```
```css
.wrapper1[fill-up-small] {
opacity: 0.5;
}
.wrapper1[fill-up-large] {
transform: rotate(5);
}
.wrapper2 {
position: relative;
padding-top: 56.25%; /* The ratio of the image must be known. Alternatively, the image can be cropped with `object-fit: cover` to arbitrary aspect ratio.*/
}
.wrapper2 .image {
position: absolute;
top: 0;
left: 0;
width: 100%;
height: 100%;
}
```ember-container-query:
Uses [ember-element-helper](https://github.com/tildeio/ember-element-helper) as a polyfill for [RFC 389](https://github.com/emberjs/rfcs/blob/master/text/0389-dynamic-tag-names.md) ([tracking](https://github.com/emberjs/rfc-tracking/issues/42)):
```hbs
<ContainerQuery @tagName="img" src alt/>
```ember-element-query:
```hbs
<img {{element-query}} src alt>
```Using both width and height in a rule for template transformation
ember-fill-up:
```hbs
<FillUp
class="my-component"
@breakpoints={{hash
smallWidth=(fill-up-lt 350)
mediumWidth=(fill-up-between 350 700)
largeWidth=(fill-up-gte 700)
smallHeight=(fill-up-lt 199 dimension="height")
mediumHeight=(fill-up-between 200 399 dimension="height")
largeHeight=(fill-up-gte 400 dimension="height")
}}
as |F|
>
{{#if (and F.breakpoints.smallWidth F.breakpoints.largeHeight)}}
I am thin and tall.
{{/if}}
</FillUp>
```ember-container-query:
```hbs
<ContainerQuery
class="my-component"
@features={{hash
smallWidth=(cq-width max=349)
mediumWidth=(cq-width min=350 max=699)
largeWidth=(cq-width min=700)
smallHeight=(cq-height max=199)
mediumHeight=(cq-height min=200 max=399)
largeHeight=(cq-height min=400)
}}
as |CQ|
>
{{#if (and CQ.features.smallWidth CQ.features.largeHeight)}}
I am thin and tall.
{{/if}}
</ContainerQuery>
```ember-element-query:
```hbs
<ElementQuery
@dimension="both"
@sizes={{hash small-width=0 medium-width=350 large-width=700}}
@sizesHeight={{hash small-height=0 medium-height=200 large-height=400}}
as |EQ|
>
{{#if (and EQ.to-small-width EQ.from-large-height)}}
I am thin and tall.
{{/if}}
</ElementQuery>
```
When usign default sizes, this gets even shorter:
```hbs
<ElementQuery @dimension="both" as |EQ|>
{{#if (and EQ.to-s EQ.from-l-height)}}
I am thin and tall.
{{/if}}
</ElementQuery>
```Contributing
Tools
Use Volta and Yarn.Installation
git clone <repository-url>cd ember-element-queryyarn
Linting
yarn lint:hbs— only templatesyarn lint:ts— only TypeScript compiler (tsc)yarn lint:eslint— only ESLint (including Prettier andtypescript-eslint)yarn lint— everything
Running tests
ember test– Runs the test suite on the current Ember versionember test --server– Runs the test suite in "watch mode"ember try:each– Runs the test suite against multiple Ember versions
Running the dummy application
ember serve- Visit the dummy application at http://localhost:4200.
For more information on using ember-cli, visit https://ember-cli.com/.
License
This project is licensed under the MIT License.Credit
Implemented by Andrey Mikhaylov (lolmaus) and contributors.Thanks to Chad Carbert (@chadian) and Isaac Lee (@ijlee2) for feedback, ideas, brainstorming and criticism.
This addon's demo is borrowed from ember-container-query per @ijlee2's generous permission.
Sponsored in part by @kaliber5, https://kaliber5.de.
