Table View displays rich text as HTML and would not allow pasting or editing of rich text. Reproducible: Always == CASE 1: Table View displays rich text as HTML Steps to Reproduce: 1. Paste a rich text to a form's Text Editor widget in form data view (currently the Text Editor does not support formatting actions so pasting is needed); the widget should have data field assigned for table T 2. Accept changes 3. Go to the table view of the table T Actual Results: The text in record(s) that were filled in step 1 is displayed as HTML, i.e. starts with: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" ... Expected Results: The HTML is rendered as rich text. For values not having the HTML DOCTYPE prefix, plain text should be displayed. == CASE 2: Table View would not allow pasting or editing of rich text Steps to Reproduce: 1. Go to a table view of the table T, text column 2. Paste some rich text content into a cell of the column (currently the Text Editor does not support formatting actions so pasting is needed) Actual Results: The text gets pasted as plain text. Expected Results: The text gets pasted as rich text and immediately rendered as such. Currently the Editor does not support formatting actions but this is a topic for another report. Related bug: https://bugs.kde.org/show_bug.cgi?id=309174
Moved to 2.8.1 plans.
Can I take it? :)
Created attachment 92024 [details] attachment-3435-0.html Sure On Tuesday, 14 April 2015, Wojciech Kosowicz <pcellix@gmail.com> wrote: > Wojciech Kosowicz changed bug 312134 > What Removed Added > CC pcellix@gmail.com > Assignee kexi-bugs@kde.org pcellix@gmail.com > > Comment # 2 on bug 312134 from Wojciech Kosowicz > > Can I take it? :) > > ________________________________ > You are receiving this mail because: > > You reported the bug. > You are watching someone on the CC list of the bug. > You are watching the assignee of the bug.
What are your plans with this fix, @Wojtek?
I'll start working on it right away :)
Cool! Assigning.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.