#HAVELLS (weekly)
- Breakout from Supply zone
- Tarding All time high
- Strong Bullish trend
- Massive volume accumulations
- Buy above 1235
- Stoploss 1175
- Target 1267/1293/1347/1400+
More from Himanshu Chauhan
More from Havells
HAVELLS
Double Top Buy, Super Pattern - Bullish & T20 Pattern - Bullish above 1266.91 daily close on 1% Box Size chart. https://t.co/78Tb2dKZkm
Double Top Buy, Super Pattern - Bullish & T20 Pattern - Bullish above 1266.91 daily close on 1% Box Size chart. https://t.co/78Tb2dKZkm
HAVELLS
— Saket Reddy (@saketreddy) January 5, 2021
DTB above 921.43 daily close (Closed above it today) on 1% box size chart, DTB active on 3% chart.
I would still stick to my earlier point that 1250-1300 is the next logical supply zone. https://t.co/9SyiHd90qg pic.twitter.com/LjtqKvX1Ld
HAVELLS
Double Top Buy above 1485.56 daily close on 1% Box Size chart. https://t.co/zY8JwRIZUu
Double Top Buy above 1485.56 daily close on 1% Box Size chart. https://t.co/zY8JwRIZUu
HAVELLS
— Saket Reddy (@saketreddy) August 30, 2021
Double Top Buy, Super Pattern - Bullish & T20 Pattern - Bullish above 1266.91 daily close on 1% Box Size chart. https://t.co/78Tb2dKZkm pic.twitter.com/4lWz25jGgk
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.