#Bhel 6% up if daily candle close above 60 to 61 then 67 or 80 lvls coming
@KUTrack @masterchefsd @cat_trader007 @AnshumanCharts @IntradayGeeks @charts_breakout @Anshi_________ @Kavitastocks @TechCheckByNiti @ipo_mantra
#bhel morning star pattern on support looking good for swing @masterchefsd @Anshi_________ @AnshumanCharts @charts_breakout @JayneshKasliwal @kuttrapali26 @cat_trader007 pic.twitter.com/OWlgGLI1MS
— preet (@preet8699) September 22, 2021
More from Bhel
#Bhel - Falling from 79.55 now at 55
Chart wise labeling for 1,2,i,ii for now - counts invalid if falls further to 38. In that case will take a fresh look.
#Nifty #Elliotwave #Chart https://t.co/2mvKfAs3wA
Chart wise labeling for 1,2,i,ii for now - counts invalid if falls further to 38. In that case will take a fresh look.
#Nifty #Elliotwave #Chart https://t.co/2mvKfAs3wA

Holding 29, major wave 2 looks over. Will you believe if I say ATH will come? But let's go step my step - 80-130-200 \U0001f600#Bhel pic.twitter.com/3KPCYeDoDp
— Harsh Mehta (@_Harsh_Mehta_) February 4, 2021
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.