Issue metadata
Sign in to add a comment
|
Chromevox slows down when writing posts via any blog hosting platform when writing posts with over 5000 words via HTML mode
Reported by
blindfai...@gmail.com,
Mar 21 2017
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 56.0.2924.110 Reproduction Steps: 1. Enable Chromevox. 2.Type Ctrl-N or Ctrl-T to open a new tab. Type a URL to a website what you own. For example; your site is located on Blogger: example.blogspot.com/, or type in a URL of your own domain what you own,--if you were using Self-hosted WordPress: example.com/. 3.Log into your control panel, and create a new post. If you were using self-hosted WordPress... go to the posts section, and go to the "add new" link. 4. Enter a title for your post,--whether if you were writing a post like a little book, or news report. 5. Switch to the text view, and write your content in HTML. Keep writing your content,--until you reached over 5000 words. Listen and analyze why Chromevox is slowing down. This step can work with any Chrome Device. Varify if Chromevox is responding to a long post editor. Varify if Chromevox is NOT taking up memory, or processing power. And varify if Chromevox is doing its job. Start from typing slow on this post, and publish it. 6. Repeat these steps and gradually type faster. For Blogger Users: Go to blogger.com, and create a new post. Give a post a title. Switch to HTML mode, and write your content. Save on a regular basis. You may need to experiment how much words you can reach when writing your posts. Publish it. The expected output: Chromevox will NOT take up processing power,--whether which model of Chrome device is chosen by a user. As the post editor reaches over 5000 words... Chromevox responses like it should. What went wrong: Chromevox starts to slow down, and take up resources,--resulting with a slight delay of jumping to the text field itself. How often this problem occurs: Always,--recurring via recent Chrome versions,--including older versions. Are any possible workarounds: There's no possible workarounds. Does this issue impact users: This issue may impact users who were constantly writing extremely long posts on their websites. For example; long articles that focus on cutting pollution. Or in some cases, writing advanced content with complex formatting, and lots of sourcecode.
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
May 8 2017
,
Sep 22 2017
Hello, Thanks for submitting this, here's how I am looked into it further. I could not reproduce the behavior so I am resolving this issue. Please feel free to reopen it if you are still experiencing any problems. Also, please try updating to the latest version of ChromeOS to see if the issue persists: https://support.google.com/chromebook/answer/177889?hl=en First, the test setup: I don't have a blogger site so I am using this example WYSIWYG editor to simulate the experience: https://www.froala.com/wysiwyg-editor/examples/full-featured I also wanted to simulate the experience of writing 5000 words so I generated 5000 dummy words on this website: http://www.lipsum.com/ and copied it to the clipboard. Next, the test to compare performance with using ChromeVox vs without using ChromeVox when pasting in 5000 words at a time into the WYSIWYG editor: # Without ChromeVox on, keep pasting in 5000 word chunks until there is a delay in copy/pasting. It took me until 6 pastes before I saw any noticeable slowdown, and at that it was brief. This means I "typed" 30,000 words without much issue. # I cleared the website and turned ChromeVox on and started pasting in units of 5000 words like before. I also got to 30,000 words by the time I noticed any slight slowdown. Therefore, I consider that the experience is pretty much identical in both cases and that I'm not uncovering specific problems with ChromeVox performance here. Thanks, Laura |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ni...@jaberspace.com
, Mar 22 2017