docs(windows): update kb0076 to include log capturing on firefox#2569
docs(windows): update kb0076 to include log capturing on firefox#2569Meng-Heng wants to merge 3 commits into
Conversation
…keyman keyboard" This reverts commit df82f92.
User Test ResultsTest specification and instructions User tests are not required |
Meng-Heng
changed the title
| @@ -1,9 +1,9 @@ | |||
| # HOWTO: Run Debugging in Keyman Desktop | |||
| # HOWTO: Run Debugging in Keyman Desktop and Firefox | |||
There was a problem hiding this comment.
I think we should change it to "Keyman for Windows" instead of "Keyman Desktop" (throughout this doc).
| # HOWTO: Run Debugging in Keyman Desktop and Firefox | |
| # HOWTO: Run Debugging in Keyman for Windows and Firefox |
| **NOTE**: Please only perform send Keyman Support a log file if we request it. We don't have the resources to review unsolicited log files! | ||
| ## Capture a log in Firefox | ||
|
|
||
| #### Only follow this if the issue is related to Google products or other web applications. |
There was a problem hiding this comment.
I find this sentence confusing. Why the focus on Google products? Shouldn't I follow these steps if I have problems typing on a normal website? And in general, when should I not follow these steps?
There was a problem hiding this comment.
Yes I think remove this sentance or it should just say
"These steps are for issues you have that are reproducilbe using Firefox"
MengHeng the main times I have asked for this debug capture in the forums is when users have had problems using Firefox and Googe Docs/Sheets. However, I also used it for just contentedable fields in Firefox (so general web pages really).
It is most usefull for finding issues with Firefox. However it could be usefull if there is a particullar webpage/application that doesn't work with Keyman and any browser and you could use Firefox just for its abillity to capture a log.
|
|
||
| #### Only follow this if the issue is related to Google products or other web applications. | ||
|
|
||
| 1) Open a testcase in a tab, e.g. Google Docs or Sheets |
There was a problem hiding this comment.
| 1) Open a testcase in a tab, e.g. Google Docs or Sheets | |
| 1) Open a testcase in a tab, e.g. Google Docs or Sheets, Website with issue |
|
|
||
| 5) If you see “Start logging” button in top of the page, click it. | ||
|
|
||
| 6) Back to the tab loaded the testcase with mouse |
There was a problem hiding this comment.
| 6) Back to the tab loaded the testcase with mouse | |
| 6) Go back to the tab loaded with the testcase using the mouse |
|
|
||
| 6) Back to the tab loaded the testcase with mouse | ||
|
|
||
| 7) Click the editor and do the minimum steps to reproduce the bug |
There was a problem hiding this comment.
| 7) Click the editor and do the minimum steps to reproduce the bug | |
| 7) Do the minimum steps to reproduce the bug |
|
|
||
| 7) Click the editor and do the minimum steps to reproduce the bug | ||
|
|
||
| 8) Back to the tab loaded `about:logging` with mouse |
There was a problem hiding this comment.
| 8) Back to the tab loaded `about:logging` with mouse | |
| 8) Go back to the tab loaded `about:logging` with mouse |
4 participants
Sources
Context
I found two topics that have the instruction to capture logs in Firefox. Would this fit in the knowledge base?
This PR is adding
Capture a log in Firefox, changing the title to includeFirefox, and updating syntaxes forWarningandNote.This is ready for review.
Test-bot: skip