[Libreoffice-ux-advise] [Bug 95861] Writer Web -- rework HTML export and import filters to use HTML 5 and inline CSS3 styles

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=95861

Buovjaga <todventtu at suomi24.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gerry.treppel at googlemail.co
                   |                            |m, todventtu at suomi24.fi

--- Comment #9 from Buovjaga <todventtu at suomi24.fi> ---
(In reply to Tomaz Vajngerl from comment #8)
> (In reply to Gerry from comment #7)
> > I oppose the removal of the web view and HTML source view/editing. It is a
> > quite handy feature, which I frequently use and really like. I am quite sure
> > that other people are using it, too.
> 
> What do you use it for?

Gerry posted his use case here:
https://wiki.documentfoundation.org/Talk:Proposals_for_removing_features

"I have all documents in Libreoffice (including all their layout and
formatting, of course). It is very handy to move (parts of) documents over to
Writer/Web, switch to HTML source code, edit/refine the source code, switch
back to Writer/Web view to see how it looks, switch back to source code and
copy the relevant part of the source code to use it further for websites or
CMS. In my opinion, only the tight integration with the office suite allows to
not lose formatting in this kind of workflow."

Usually CMSes include embedded WYSIWYG rich text editors like CKEditor or
TinyMCE. If there are problems with the CMS editors accepting pasted formatted
content from LibreOffice, bugs can be filed against them.

Writer/Web cannot be used as a reliable preview of how something looks like in
a browser and to bring it to such a state would require a huge investment of
developer resources.

We cannot compete with the developer tools in browsers. Honing them has taken
dozens, probably hundreds of man years.
Interaction with JavaScript, responsive design etc. - there is no way we could
implement this.

We should not try to compete with desktop WYSIWYG editors as they are very
niche and ill-suited for web design and development.

If they wish, developers can shed light on the technical challenges regarding a
decision to amp up our HTML WYSIWYG capabilities.

-- 
You are receiving this mail because:
You are on the CC list for the bug.