31099 2009-11-03 22:24:51 -0800 [Qt] Add a way to access text nodes tree with QWebElement 2014-03-17 16:16:53 -0700 1 1 1 Unclassified WebKit WebKit Qt 528+ (Nightly build) All All RESOLVED INVALID Qt, QtTriaged P3 Enhancement --- 48957 1 benjamin webkit-unassigned abecsi benjamin cmarcelo hausmann kenneth kling paul.masurel robert skyul tonikitoo oldest_to_newest 160319 0 benjamin 2009-11-03 22:24:51 -0800 There is no way to access text nodes children of QWebElement. This limit the use of the API. Here is an example How do I get "prefix" and "suffix" with QWebElement in the following snippet: "<div> prefix <img src=""/> suffix </div>" To solve this, we could introduce a new class to iterate over the content of the QWebElement (QWebElementIterator || QWebElementCusor). E.g.: QWebElementCursor cursor(element); while (cursor.next()) { if (cursor.isText()) { cursor.setHtml(QString("<p>%1</p>").arg(cursor.text())); //? int selectionOffset = cursor.textSelectionBeginning(); } else if (cursor.isElement()) { QWebElement child = cursor.element(); child.encloseWith("<div>"); } } 161559 1 kenneth 2009-11-09 06:36:46 -0800 4.7 stuff definately. I have also had requests for iterating the text itself, and querying for size, position etc. This is useful for ebook readers etc that want to split text blocks to fit as much contents on a page as possible, and put all overflow to the next page. There are probably more usecases for this. 306370 2 tonikitoo 2010-11-08 14:23:07 -0800 Maybe it should be not blocking 2.1 API metabug(?) 663046 3 paul.masurel 2012-07-04 10:05:32 -0700 Meanwhile, has anyone found any workaround? 663160 4 benjamin 2012-07-04 14:04:25 -0700 (In reply to comment #3) > Meanwhile, has anyone found any workaround? I think this is pretty much dead after the switch of focus to WebKit2. I don't know what API will replace QWebElement (if any). I think the only way to workaround this is to use JavaScript to modify the DOM. 975095 5 jturcotte 2014-02-03 03:15:53 -0800 === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.