Same Problem, New Recurrence (bible text can't be selected for copy)
I had this problem with a short section of text in the past, but encountered it again today in church.
I was in my ESV at 1 Sam. 4. Verses 1-20a cannot be selected in order to copy them.
Here is what I normally see when I touch and hold a word. I can then grab the 'handles' and select the text I want to copy to my Notability app.
Here's what I see in 1 Sam 4:1-20a. It can't be selected. I just re-tried it at home (on a different wi-fi connection) and I'm getting the same results.
This is frustrating, as I copy the text during the sermon for my sermon notes. Couldn't do it today.
Eating a steady diet of government cheese, and living in a van down by the river.
Comments
-
-
i've had this happen in various odd places, all non-Bibles though.
"The whole modern world has divided itself into Conservatives and Progressives. The business of Progressives is to go on making mistakes. The business of Conservatives is to prevent mistakes from being corrected."- G.K. Chesterton
0 -
If you turn Scrolling View off does the issue still occur?
0 -
If you turn Scrolling View off does the issue still occur?
With scrolling view off, the behavior is normal (I can select the text).
When I turned scrolling view off, I noticed it went to two columns (only one column shows in scrolling view, and the column setting was 'Auto' when I switched scrolling view off). I changed the columns (scrolling view off) to 1 from Auto, and the problem text was behaving normally (i.e. could be selected).
Is this a bug or a rarely-occurring quirk?
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
When I turned scrolling view off, I noticed it went to two columns (only one column shows in scrolling view, and the column setting was 'Auto' when I switched scrolling view off).
This is normal, unless the font size is set to be quite large.
Is this a bug or a rarely-occurring quirk?
This is a bug, I believe a case already exists for it (if not I will create one).
0 -
This issue is fixed in the 5.1 version (currently in Beta).
Version 5.0.2: -
Version 5.1.0: -
0
