# Firefox Nightly で CTRL-C が「トピック作成」ショートカットをトリガーする問題
**URL:** https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584
**Category:** Support
**Created:** [2018 年 1 月 21 日午後 12:53 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584 "2018-01-21T12:53:57Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@jonathon](https://meta.discourse.org/u/jonathon)
#### Post date: [2018 年 1 月 21 日午後 12:53 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/1 "2018-01-21T12:53:57Z")
## Description
Starting over the last few days, Discourse will open the New Topic composer when the user presses CTRL+C.
Pressing only C also triggers the New Topic composer as expected.
## Related change?
On first glance it appears to be related to:
[https://github.com/discourse/discourse/commit/ff91c43087ea6895c0380faa0e171747ca5daf8e](https://github.com/discourse/discourse/commit/ff91c43087ea6895c0380faa0e171747ca5daf8e)
though that’s supposed to enable SHIFT+C…
## Discourse info
Version [v2.0.0.beta1 +202](https://github.com/discourse/discourse/compare/7b05b12d3c33f20a7578707210d9dce26776429e...tests-passed)
Ubuntu 16.04 (64-bit)
Docker CE 17.12 (overlayfs2)
Bytemark Cloud VPS
## What should happen
Discourse should not capture CTRL+C.
## What currently happens
Discourse interprets CTRL+C as C.
## Steps to replicate
1. Press CTRL+C (or CMD+C for Mac?);
2. Observe New Topic composer appears.
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [2018 年 1 月 21 日午後 1:16 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/2 "2018-01-21T13:16:54Z")
Im not familiar with the shortcut codepath, but reading the commit I see C and not shift+c, do you think this is the cause @riking ?
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2018 年 1 月 21 日午後 5:07 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/3 "2018-01-21T17:07:05Z")
Oh, yeah probably. I guess I wasn’t looking too closely at the requirements for the shortcut names…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 1 月 22 日午前 12:44 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/4 "2018-01-22T00:44:53Z")
I am not having an easy time reproducing this, what browser is this on, seems to work as desired on Chrome to me.
---
### Author:  [@Sailsman63](https://meta.discourse.org/u/Sailsman63)
#### Post date: [2018 年 1 月 22 日午前 12:59 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/5 "2018-01-22T00:59:58Z")
Windows 10, Firefox Quantum (57.0.4) ,Ctrl + C copies to clipboard as expected. C opens the composer. Shift + C does nothing.
---
### Author:  [@jonathon](https://meta.discourse.org/u/jonathon)
#### Post date: [2018 年 1 月 22 日午前 1:34 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/6 "2018-01-22T01:34:37Z")
I’m hitting it with Linux 64-bit Firefox Nightly 59a1 (2018-01-21). One other person [has reported the same](https://forum.manjaro.org/t/pressing-ctrl-c-to-copy-from-forum-opens-new-blank-post-template/38667?u=jonathon) with Firefox 57.0.4 (which triggered this report in the first place).
It does the same thing for me here on [meta.discourse.org](http://meta.discourse.org) so it’s not specific to our instance, though I’ll admit it might be a browser quirk. However, the fact I encountered the same behaviour around the same time as another user makes me suspicious.
I’ll roll through some more browsers/settings tomorrow; with fresh profiles neither Chromium (63.0.3239.132) nor Firefox (57.0.4) exhibit the same behaviour for me.
Edit:
Little update: it does appear to be a browser setting. Nightly 2018-01-21 and a clean profile doesn’t exhibit the issue, but a `-safe-mode` start (no extensions) with my normal profile does.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018 年 1 月 22 日午前 1:38 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/7 "2018-01-22T01:38:27Z")
> [@jonathon](#):
>
> with fresh profiles neither Chromium (63.0.3239.132) nor Firefox (57.0.4) exhibit the same behaviour for me
Yeah we are going to need a repro here, without it we are just guessing.
---
### Author:  [@jonathon](https://meta.discourse.org/u/jonathon)
#### Post date: [2018 年 1 月 22 日午後 1:46 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/8 "2018-01-22T13:46:03Z")
This appears to be a quirk in some profile setting and Firefox Nightly (~2018-01-21/22). Using the same profile in 57.0.4 doesn’t exhibit the same issue.
I can’t see which setting would make this happen so it may well just be a Nightly quirk; the other user who had the issue no longer does with Firefox Nightly, so who knows…
Apologies for the noise… 😣
* * *
Edit, someone else just started having the issue with 59b2 (Developer). No idea what’s going on here. I’ll post back here if I can find some sort of pattern to it.
* * *
Edit, it’s a Firefox thing. I’ve just seen the same behaviour on GitHub, so “something” is sending the wrong keystrokes to the page.
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2018 年 1 月 23 日午後 11:00 UTC](https://meta.discourse.org/t/ctrl-c-triggers-create-topic-shortcut-in-firefox-nightly/78584/9 "2018-01-23T23:00:00Z")
This topic was automatically closed after 30 hours. New replies are no longer allowed.