css - LESS, Media Queries, and Performance -


i got started lesscss, , i've been having quite bit of success in regards how clean , readable css has become. however, don't think i'm using less fullest advantage.

i'm in process of coding first fully-responsive site using less, , i'm concerned performance , speed. one thing note don't stick "breakpoint" methodology - scale things , down until break, write css fix them; results in anywhere 20 - 100 media queries.

i'd start using less nest media queries inside elements, such example below:

.class-one {     //styles here      @media (max-width: 768px) {         //styles width     } } .class-two {     //styles here      @media (max-width: 768px) {         //styles width     } }

through initial testing, have found when reviewing compiled css output - methodology results in multiple (many!) instances of @media (max-width: ___px). have scoured internet, , haven't found explicitly explains performance implications of nesting/bubbling media queries.

update 1: realize more css information results in larger css file download - i'm not worried site load time sole metric. i'm more interested in browser's handling of memory , performance after dom ready.

update 2 & semi-solution: found this article discusses 4 main categories of css selectors , efficiencies. highly recommend read helped me sort out how best tackle over-media-query'd css.

so question this: after dom ready, having many media queries in compiled stylesheet affect load times & performance?

its impossible give totally accurate answer.

when asking performance typical answer profile , see get. fix slowest part first, repeat.

you can profile css selectors in chrome developer tools:

enter image description here

ultimately don't think media queries have anywhere near impact on performance compared complicated selector.

you can see more information writing efficient css here:

https://developers.google.com/speed/docs/best-practices/rendering

also regards file size , repeated css, gzip almost nullifies gzip algorithm works best repeated data.


Comments

Post a Comment

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

i've tried various ways coerce xterm (versions 285 , 292) copy selection clipboard clipboard whenever press ctrl-shift-c. promising way far has been, in ~/.xresources, put this: xterm*vt100.translations: #override \ ctrl shift <keypress> c: copy-selection(clipboard) \n\ ctrl shift <keypress> v: insert-selection(clipboard) ctrl-shift-v works perfectly, copying has nuance... if restart xterm, highlighting text puts things in primary clipboard; expected, proper, default behavior. if hit ctrl-shift-c, copies current selection clipboard clipboard. the bug, however, if highlight text after first time pressed ctrl-shift-c, you'll see highlighting copies both primary and clipboard. cannot figure out how stop xterm updating clipboard upon selection... , doesn't make sense me in first place. i said, @ specific point in time, copy selection clipboard... yet starts updating automatically upon selection after doing once... anyone have workaround...
Read more

c++ - qgraphicsview horizontal scrolling always has a vertical delta -

Image
i've subclassed qgraphicsview custom canvas used in cad application. i've reimplemented qgraphicsview::wheelevent check keyboard modifiers control key and, if control key pressed, zoom. i'm trying implement horizontal scroll when user holds shift , uses wheel. the problem i'm having horizontal scrolling always scrolls 0.279. not huge problem, hugely annoying , points else being wrong. so, here questions: is right way implement horizontal scrolling? if not, is? how eliminate delta of 0.279? thanks in advance. code , sample output below void myview::zoom(int delta) { double factor = pow(1.2, delta/abs(delta)); this->scale(factor, factor); } void myview::scrollhorizontal(int level) { qpointf center = maptoscene(viewport()->rect().center()); qdebug() << "center: " << center.x() << ", " << center.y(); centeron(qpointf(center.x() - level, center.y())); } void myview::wheelevent(qwheeleve...
Read more