Bug 4923 - Document troubleshooting for Web Access
Summary: Document troubleshooting for Web Access
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Documentation (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Aaron Sowry
URL:
Keywords:
Depends on: 5172 7490
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-02 13:04 CET by Karl Mikaelsson
Modified: 2020-04-24 09:07 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments

Description Karl Mikaelsson cendio 2013-12-02 13:04:01 CET
Prerequisites, installation, configuration, troubleshooting, etc.
Comment 1 Pierre Ossman cendio 2013-12-02 13:54:11 CET
Probably want to clean up/clarify the web technologies used as well. HTML5 is a very buzzword-y term that has many problems:

 - It's very buzzword-y and it's meaning very unclear for many audiences.

 - The current HTML (and related) specification is developed both in W3C and WHATWG. The latter prefers a living specification without versions, and so just call it "HTML".

 - Our client uses technology that is covered by more specifications than just the HTML one. A "HTML5" compliant browser could very well not support our client.

So we should probably use something more general like "modern web technologies" and list more exact requirements.
Comment 2 Karl Mikaelsson cendio 2013-12-17 09:54:17 CET
Is this list of supported platforms still correct? Is Firefox mobile so different  from the desktop browser that it needs a separate entry?

> • Internet Explorer 10 or newer (Desktop Mode)
> • Internet Explorer 10 or newer (Metro Mode)
> • Firefox 11 or newer
> • Firefox Mobile 11 or newer
> • Google Chrome 16 or newer
> • Safari 6 or newer

- /webaccess/logging is not fully documented.

- Screenshots and descriptions of the client UI is missing.
Comment 3 Samuel Mannehed cendio 2017-04-20 13:11:37 CEST
Some of the problems mentioned here have been addressed over time. The areas that I can see that we are still lacking in are:

* Troubleshooting
* Documentation for webaccess logging

And lastly, and perhaps most importantly:

* Screenshots and descriptions of the interface
Comment 4 Pierre Ossman cendio 2020-04-24 09:07:04 CEST
Usage documentation has now been fixed, so the only thing that remains is a troubleshooting section.

Note You need to log in before you can comment on or make changes to this bug.