[jbosstools-issues] [JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

[Radim Hopp (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087710#comment-13087710 ] 

Radim Hopp commented on JBIDE-19990:
------------------------------------

Sooo.. We've made a progress here!
On Vlado's machine, everything worked as expected, but I finally figured out what caused my machine to fail in this case.
As I stated previously, google-chrome was configured as default browser in KDE (Plasma 5) settings and it was used as default browser by all applications respecting that settings. What I had different than Vlado is default application for text/html mimetype. There I had konqueror as default application for handling text/html mimetype (and I think this is default application in Plasma 5 for handling it).
When I changed this to google-chrome or firefox, everything was working fine.

In conclusion: "See JBoss Tools Visual Editor FAQ" link is not working IF Konqueror is configured as default application for text/html mimetype.

> "See JBoss Tools Visual Editor FAQ" link is not working.
> --------------------------------------------------------
>
>                 Key: JBIDE-19990
>                 URL: https://issues.jboss.org/browse/JBIDE-19990
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, visual-page-editor-core
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Radim Hopp
>            Assignee: Radim Hopp
>             Fix For: 4.3.0.Beta2
>
>
> When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here:  http://i.imgur.com/F2l9Hgi.png).
> This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this:
> _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)