Thread: doubled id
View Single Post
Old 08-11-2016, 02:49 PM   #19
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,601
Karma: 5703586
Join Date: Nov 2009
Device: many
That is horrible ....

I'd say this is yet another nail in the coffin for BV. I will study the BookView code but this could be coming from hitting enter inside a QWebkit widget when live editing a dom document (which is what BV is actually doing).

KevinH


Quote:
Originally Posted by DiapDealer View Post
It's got nothing to do with the splitting, by the way. The elements with duplicate ids are there at the end of step 2.

It also doesn't matter if you place the cursor before or after the text and hit enter.

1) open a new empty epub
2) give the existing p element an id of some kind (any id)
3) switch to Book View and hit enter 3 times
4) switch back to Code View and look at the code

Book View has behaved this way at least as far back as 0.7.x (and probably since the beginning). Hitting enter when in Book View will create a new (the same) element which has the exact same attributes as the element your cursor was in when you hit enter.
KevinH is offline   Reply With Quote