MobileRead Forums - View Single Post

DiapDealer · Today, 08:23 AM

This seems to be some sort of accumulating one-off thing. If you move the vale class closer to the top of the css file, F3 finds it OK. But the cursor doesn't seem to go to the beginning of the css class.

As you move the vale class further and further down the css file, finding with F3 results in the cursor moving further and further into the class itself. Until it starts "finding" classes AFTER "vale".

Once you move vale to the end of the css file (or close to it), the F3 Find in Style feature can't position the cursor without going past the end of the file, so it bounces to the top.

I don't know why yet, but I would suspect any Find in Style search would fail to reposition to the last class in a css file of any significant length.

Doesn't seem to be a bug new to Sigil 2.8.0, thank goodness. I'm able to reproduce it in 2.7.6.

Today, 08:23 AM	#2
DiapDealer Grand Sorcerer Posts: 29,489 Karma: 212177546 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	This seems to be some sort of accumulating one-off thing. If you move the vale class closer to the top of the css file, F3 finds it OK. But the cursor doesn't seem to go to the beginning of the css class. As you move the vale class further and further down the css file, finding with F3 results in the cursor moving further and further into the class itself. Until it starts "finding" classes AFTER "vale". Once you move vale to the end of the css file (or close to it), the F3 Find in Style feature can't position the cursor without going past the end of the file, so it bounces to the top. I don't know why yet, but I would suspect any Find in Style search would fail to reposition to the last class in a css file of any significant length. Doesn't seem to be a bug new to Sigil 2.8.0, thank goodness. I'm able to reproduce it in 2.7.6. Last edited by DiapDealer; Today at 08:26 AM.