Skip to content
This repository has been archived by the owner on Sep 10, 2022. It is now read-only.

Section for What forces layout / reflow #23

Open
yeomann opened this issue May 28, 2016 · 10 comments
Open

Section for What forces layout / reflow #23

yeomann opened this issue May 28, 2016 · 10 comments

Comments

@yeomann
Copy link

yeomann commented May 28, 2016

Hi guys, from this question stack overflow question, may i suggest if we can add section for something like Layout trashing. For example, On site it is mentioned that transform property doesn't cause geometry change i.e no layout re-flow but i think it's worth mentioning that if its called through JavaScript then it does!
Let me know your thoughts if i can contribute as well or if i am wrong?

@surma
Copy link
Contributor

surma commented May 28, 2016

Changing a transform (even through JS) does not force relayout or repaint in Chrome. The gist by Paul Irish says that getComputedStyle() does cause relayout if a transform is set.

Currently, csstriggers shows that Gecko, Edge and Webkit do relayout when you change transform. However, @paullewis and I are believe that to be a bug of the respective DevTools and is not actually true.

@gregwhitworth
Copy link

Hey @surma and @paullewis I do think it's worth adding this section. We should document what APIs cause a reflow, eg: getBoundingClientRect() offsetHeight, etc as we see the common read-modify-write pattern on the web and it would be nice if this was included.

@surma
Copy link
Contributor

surma commented Jan 19, 2017

@gregwhitworth
Copy link

Ok, I'm not a hardcore designer but I know my away Photoshop - here's a quick mockup, don't focus on the data it's merely for finalizing the design. Let me know your thoughts. I recommend switching the domain to *triggers.com which most are actually available since technically these aren't CSS triggers but do force a style recalc and possibly layout. Let me know your thoughts @surma and @paullewis

css-triggers

@surma
Copy link
Contributor

surma commented Jan 21, 2017

Yeah, @paullewis had already been messing around with potential domain names. Any suggestions welcome. EngineTriggers doesn’t sound too bad, but I’d like to convey that it’s web-related somehow.

Design looks A+ to me, great stuff :)

@gregwhitworth
Copy link

This feels like the need for a twitter poll, UA Triggers, Browser Triggers, Pipeline Triggers

@surma
Copy link
Contributor

surma commented Jan 21, 2017

Ha, let’s see what happens.

@surma
Copy link
Contributor

surma commented Jan 26, 2017

So, technically “Browser triggers” won, but I liked the idea of just getting “jstriggers.com” (which I just bought) and having both URLs link to the same site. WDYT?

@oldergod
Copy link
Contributor

oldergod commented Jan 27, 2017

Browser triggers is a mouthful to me. I like the idea having multiple domains linking to a same site.

@gregwhitworth
Copy link

Be honest with everyone, trigger just makes me think of chiggers so whatever works for everyone else I'm good with. Just have the title swap out then when you change the tab * Triggers. I'm assuming you all are able to insert the data from Paul's post into the format?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants