danhper / atomic-chrome Goto Github PK

When you try to use atomic-chrome in another Chrome extension (eg. Tampermonkey), this bug appers:

Unchecked runtime.lastError while running tabs.executeScript: Cannot access contents of url "chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/options.html#nav=b9a5ed01-1683-458e-acd3-42584629080e+editor". Extension manifest must request permission to access this host.
at chrome-extension://lhaoghhllmiaaagaffababmkdllgfcmc/scripts/background.js:59:16

Any idea how to work around this?

• which flavor of linux
• any other packages/plugins you've got installed

not an issue at all, but thought your setup was cool

Tested in Google Inbox.

I had the extension installed for Microsoft chromium-based Edge. Now it is turned off with this warning.

Searching "Atomic Chrome" no longer yield a result for the extension.

Alternative: I am glad that GhostText still work. https://github.com/fregante/GhostText

Not sure if this issue applies to any contenteditable area or just in Workflowy. It does not occur in TextArea instances.

Steps to Replicate

1. In a Workflowy Note (shift-enter), type this text this..<that
   
   [The less-than sign is the issue]
2. Open that note in Atom via Atomic Chrome
3. Alter the text in Atom by adding a linefeed or whatever
4. Now the text will truncate before the less-than sign, so this..

Just stumbled across this and it seems loads of people enjoy it.

But I just don't get it? Whats the point/benefit of this? What problem does it solve for example? It might help my processes dramatically, if only I knew why?!

Current behaviour:
When trying to load the atomic-chrome extension manually from a git repo, it doesn't work.

I get an error message saying the following:

Error Loading Extension
Failed to load extension from: ~/git/atomic-chrome/app
Could not load background script 'scripts/background.js'.

Expected behaviour:
Should be possible to load extension from a copy of the source, or there should be instructions explaning how to make it work.

Versions:
Linux: Debian 4.9.51-1
Chrome: Version 63.0.3239.84 (Official Build) (64-bit)

Steps to reproduce:

1. Clone repo to ~/git
   git clone https://github.com/tuvistavie/atomic-chrome.git
2. Open chrome://extensions in Chrome
3. Tick "Developer Mode"
4. Click "Load unpacked Extension" and navigate to git repo on local storage

I tried both the top level directory and the app directory for this.

It doesn't work on SRWare Iron, a Chromium-source browser striped from code with privacy concernes Chrome vs Iron

I've tried on Windows 10 32 and 64 bits and with Iron 32 and 64 bits. It's installed but is completely frozen.

Hi, i am trying to use it to edit code from Opencms editor and it uses an iframe with a textarea inside. The message at the console is: content-script.js:71 Atomic Chrome does not support <iframe> (yet?)
The structure is:

<frameset>
  <frame>
  ..
    <form>
      <iframe>
      ..
        <textarea>

For users of multiple desktops like me, it's ergonomic to have separate desktops for coding and separate desktops for browsing, so on my main (browsing) screen, I have to switch to a different desktop to use the extension, making the extension pretty much useless for me.

Here is what happens:

• I press the Atomic Chrome button in the Chrome menu
• Nothing happens visually
• I switch to the most recent desktop with Atom
• The current Atom window has a new unsaved document open with the contents of the textarea.

I propose that the extension should minimally focus Atom, like clicking it in the Dock: current desktop switches to most recent desktop with Atom which is then focused. In addition, I think the extension should be able to open a new Atom window, like right-clicking it in the Dock and clicking "New Window" (would ideally be the default behavior).

@tuvistavie @alpha22jp

I used the Atomic Chrome browser extension along with the Emacs plugin with no trouble until recently, when it suddenly stopped working unexpectedly.

To determine if the problem was the Emacs plugin or the Chrome extension, I installed Atom and the Atom plugin. This didn't work either, so I concluded something was wrong with the Chrome extension.

When I click the extension button in the Chrome toolbar, or when I press the assigned keyboard shortcut, nothing happens. How do I debug this?

Chrome version: 67.0.3396.99 (Official Build) (64-bit)
Chrome extension version: 0.2.8
Operating system: macOS 10.11.6

It looks like the framework for this was added as a result of #11.

I think there just needs to be another method added?

normalizeIframe(elem) { return normalizeFrame(elem); }

There should be an option to prevent the converting of tags to text. that way the editor can be used to edit HTML and see the pages styling. I can't figure out where the tags are being converted to text so I can test myself. Thanks

Suppose we are composing a mail or drafting text in stackoverflow and we have opened the corresponding tab in atom editor. During editing session, Atom syncs with the chrome browser.
After we are done with that chrome tab, suppose we close the tab, currently, corresponding atom tab is left open. Do you think it should get automatically closed?
Just want to hear your views on this scenario.

Perhaps it can inherit configuration and plugins from your local editor? Is this crazy hard? I don't know. Would it be cool? Fuck yes.

If I open a Google Doc, launch Atomic Chrome and start typing in Atom, my text isn't shared. Would be awesome to use it with Docs!

since the icon does not show on the chat window there is not way to call it. Tried creating a keyboard shortcut and did not work either.

Why not put the activation icon in the context menu on textareas? (right-click, ctrl-click, etc)

Could eliminate the need for the toolbar icon, which seems out of place.

Great project! It would be even nicer if when a textfield was edited, the onchange event fired.

My use case is for editing markup that is previewed as html and updates live with typing.

Often in contentediable based editors the controls offered are too limited or are annoying to use, so a method to type in them using markdown would be very useful. If the text typed in Atom was run through a markdown to html converter before being sent to a contentediable that would be very convenient. Is this possible as a setting?

Thanks,
Daniel

Every time I try to edit with this extension in Brave, it fails with the error WebSocket connection to 'ws://localhost:64292/' failed:

This was on Brave version 1.21.73 Chromium: 89.0.4389.72 (Official Build) (64-bit). I have also just tested on Google Chrome version 89.0.4389.72 (Official Build) (64-bit) and it works perfectly. The same goes for the "Edit with Emacs" extension which also uses websockets on localhost. So this appears to be an issue with Brave :-(

When working with gists, or other code,
it would be better if the file in Atom already had
the correct extension.
The current register message contains title and text,
we need to add extension or something like this there.

for example, I'm editing this markdown:
https://github.com/tuvistavie/atomic-chrome/edit/master/README.md

Before atomic-chrome:

And after I click the atomic-chrome:

OS: windows 10 x64 Build10586.589
Browser: Chrome 53.0.2785.116 (64-bit)
Atom: 1.10.2 with default config
Atomic Chrome (chrome plugin): 0.2.6
Atomic-Chrome-Atom (Atom plugin): 0.3.0

Please see Other Workflowy Related Issues

Description of Problem

In Workflowy's editor for notes it wraps links, bold, italics and underline.

• Links - Links are like this <a class="contentLink" target="_blank" rel="noreferrer" href="[SITE]">[SITE]</a>... those links then get converted to text in Atomic Chrome. They then return and get wrapped again... and so on and so on.
• Formatting - Bold is like this <span class="contentBold">, while italics use contentItalics and underline uses contentUnderline
  
  Multiple formats are delimited with spaces in the class attribute, e.g., class="contentItalic contentUnderline" (as you would expect from CSS)

Solutions

All of these tags should be removed on extraction to Atom.

I'm not sure this is specific for Workflowy. Any app that loads the contentEditable with HTML should have it expunged when it's moved to Atom, I think.

Atom package atomic-chrome version: 0.3.0
Atomic Chrome extension version: 0.2.6

Clicking the browser button does nothing. Atom is open already. I tried inspecting the extension's background page via Chrome extension manager developer mode and the devtools view opens but there is nothing there, no console logs of any kind, and I am unable to use the console to run any javascript, pressing enter in the console just clears the input. It feels like the extension just isn't initialising. Any ideas?

Hello,

When I have multiple Atom windows open and I activate atomic-chrome, it opens a new tab in my oldest Atom window. I think it would make sense to open in the currently-active window (or at least have a config option for where it should open).

Mac OS 10.12 (16A323), Chrome 53.0.2785.143, Atom 1.10.2, atomic-chrome package 0.3.0, Atomic Chrome plugin 0.2.7

1. on the input form of browser, invoke shortcut of start-editing-in-atom-editor
2. want to automatically focus atom window so that I don't have to shift-tab or cmd-tab to change active app to Atom.

This looks very interesting, and it actually inspired me of a possible feature/idea.
How hard would it be to implement a way to copy to Atom what is done in Chrome? Specifically, I'd enjoy having Chrome Inspector modifications (e.g. CSS) automatically save into the Atom tab when I'm fiddling with web pages.

Problem

When the text is pulled out of a notes field in Workflowy, it looks like this

1) one thing
2) another thing
3) a third thing

but when it returns to the contenteditable div, the text comes back like this:

<div>1) one thing</div><div>2) another thing</div><div>3) a third thing</div>

While this looks right, when Workflowy subsequently saves it, it strips out the HTML tags and therefore the line breaks.

Solution

I think this problem would be solved if the text came back in with the real line-breaks intact.

Notes

I realize that special handling for one site is hard to consider, but... perhaps it's useful for other sites too?

I have no affiliation with Workflowy, but I must note that it's a great tool and, more importantly for this, it's free to use quite extensively.

Anyway, thanks in advance for even considering this, and for this awesome plug-in/package!

[Note: This issue was edited using Atomic Chrome ;)]

It would be really cool to toggle the output to html for markdown text. I've always wanted to write my emails in markdown inside gmail.

Invoking the extension on sites with titles that cannot wind up as file names results in promise errors in Atom.

On a site with site title A | B, Atom produces:

Uncaught (in promise) Error: EINVAL, open 'C:\Users\Jeremy\AppData\Local\Temp\A | B-117107-4480-1jk0sx1.ruequmcxr.md'

Removing the | solves the issue on Windows 10.

Extension does not work for https://gist.github.com

Almost embarrassed opening this issue (don't judge!) 😄

In testing this against a legacy application (using <frameset>) it did not seem to work.
However, when testing directly against the target page of the <frame src>, it worked as expected.

I'm not familiar with Chrome plugin development, perhaps this is a known limitation? (e.g. frame support)

Is this possible?