Can't type colon ":" and forward slash "/"

[dolikemedo]

What is happening?
all of a sudden, no update, no intentional change in host, I can't seem to type colon and backslash.
Every other character works.
Host recognizes the characters.

Operating system/browser name & version:
Ubuntu 22.04 , Asus K6500ZE,
uname -a
Linux BB-8 5.19.17-051917-generic #202210240939 SMP PREEMPT_DYNAMIC Mon Oct 24 09:43:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Also tested on a ubuntu 20.04

notion-enhancer and/or notion-repackaged version:

notion-app-enhanced/unknown,now 2.0.18-1 amd64 [installed]

notion-enhancer configuration (enabled/disabled mods and their settings):

I used the default guide here.
I set dark mode.
I disabled spellcheck.

It was working flawlessly, never had an issue with it.
tried so far:

• copy & paste colon or blackslash works.
• reinstalling didn't help. Same happens with notion-app-enhanced and notion-app.
• log in and out.
• change keyboard layout
• Try external keyboard

I'll try rolling back
Thanks for any help!

Edit by @dragonwocky: This also appears to affect copying/pasting with CTRL + C/CTRL + V. Notion is using the Array.at() method which is a newer JavaScript feature that isn't present in the current distribution of notion-repackaged. @dario-99 has detailed how to add a polyfill to the app to fix this below (thanks!) - #112 (comment).

[dario-99]

It happens also with my arch installation, both with Notion-app and notion-app-enhanced from the AUR.
When typing '/' the developer console prints this error:

app-f1468bbbf91e50c2009a.js:1 Uncaught TypeError: y.at is not a function
    at Object.b (app-f1468bbbf91e50c2009a.js:1)
    at ge (app-f1468bbbf91e50c2009a.js:1)
    at Pe (app-f1468bbbf91e50c2009a.js:1)
    at Object.Te (app-f1468bbbf91e50c2009a.js:1)
    at perform (app-f1468bbbf91e50c2009a.js:1)
    at app-f1468bbbf91e50c2009a.js:1
    at Function.withListenerIgnored (app-f1468bbbf91e50c2009a.js:1)
    at Module.ve (app-f1468bbbf91e50c2009a.js:1)
    at pe.handleMutation (app-f1468bbbf91e50c2009a.js:1)
    at b.handleMutation (app-f1468bbbf91e50c2009a.js:1)
    at b.delegateMutation (app-f1468bbbf91e50c2009a.js:1)
    at app-f1468bbbf91e50c2009a.js:1
    at app-f1468bbbf91e50c2009a.js:1
    at Set.forEach (<anonymous>)
    at B.emitUpdate (app-f1468bbbf91e50c2009a.js:1)
    at B.handleMutations (app-f1468bbbf91e50c2009a.js:1)
    at g.onMutations (app-f1468bbbf91e50c2009a.js:1)
    at g.stopObservingAndHandleMutations (app-f1468bbbf91e50c2009a.js:1)
    at MutationObserver.observer (app-f1468bbbf91e50c2009a.js:1)

Similiar error is printed when typing ':' occurs.
Using the web app instead seems to work flawlessly.

[ChinaNuke]

Same problem on my ArchLinux. Unable to type / and :. When I'm typing the two keys they behave like the right arrow, just moving the cursor forward.
I'm using notion-app 2.0.18-1.

[dragonwocky]

It's a bug related to the desktop app not being updated for a while, rather than something specifically caused by the notion-enhancer (which is why it doesn't happen when using the notion-enhancer as a browser extension). Thanks for reporting it here.

There's no simple fix-all yet, but as a partial workaround: you can use Ctrl + / (or ⌘ + / on macOS) to trigger the slash menu. Alternatively, you can follow @dario-99's instructions below to manually polyfill the Array.at method in the Notion app.

[hanshou101]

After my personal experimentation, I found out that the 【 Array.at() 】 API is available in the latest version of the 【Chrome browser】; but it is not supported by the 【Chromium】 engine that comes with 【Electron】.

That is, the 【Chromium】 engine of 【Notion】's 【Electron】 currently uses an older JS version; it cannot recognize the new version of the API syntax of the 【js file】 distributed by 【Notion】.

[hanshou101]

From my point of view, based on my existing front-end knowledge, I would try to make a temporary fix like this (to get myself back to work quickly).

1. Upgrade the 【Chromium】 version used by 【Electron Application】, and then repackage an 【Electron Application】.

But the problem I encountered is that I don't have the source code to build, so I can't complete the repackaging by replacing the 【electron version】 in 【package.json】.

2. By loading a 【polyfill.js】 script before 【app-[hash].js】 of 【Notion】 is loaded, the compatibility support for 【Array.at()】 syntax is completed.

So that this exception error can be bypassed very well. (Or, I can write a 【Array.prototype.at = function(idx){ ... }】 by myself; it is not a complicated thing)

The problem I encountered here is that I don't have a good means of inserting when 【html is loaded】. If it is in the Chrome browser, I can use 【TamperMonkey】 or other plug-ins, or even write a 【DevTools - Sources - Overrides】 to achieve it.

But in 【Electron】, there is no support for 【extended plug-ins】; moreover, I cannot see the existence of 【app-[hash].js】 in 【DevTools —— Sources】. (It was placed in 【DevTools —— Application —— Scripts】??? Is it just me?)

3.There are some other alternatives, such as using 【BurpSuite】 for network capture, and inserting the loading <script> of 【polyfill.js】 when 【html】 of 【Notion】 is loaded.

But that seems a bit too much trouble—I need to keep 【BurpSuite】 open all the time.

---

To sum up, here are some of my current discoveries and attempts.

[dario-99]

Searching the web i found a partial solution by imlementing manually the .at function:
Press alt and in the View menu open the developer console.

Paste in the console the following function (Found here):

function at(n) {
    // ToInteger() abstract op
    n = Math.trunc(n) || 0;
    // Allow negative indexing from the end
    if (n < 0) n += this.length;
    // OOB access is guaranteed to return undefined
    if (n < 0 || n >= this.length) return undefined;
    // Otherwise, this is just normal property access
    return this[n];
}

const TypedArray = Reflect.getPrototypeOf(Int8Array);
for (const C of [Array, String, TypedArray]) {
    Object.defineProperty(C.prototype, "at",
                          { value: at,
                            writable: true,
                            enumerable: false,
                            configurable: true });
}

As you can see the / menu works, also it types ':' correctly now.

Hope it helps.

[dario-99]

Actually found a way to inject the js function by injecting the script in the .asar file of Notion.
First i installed asar from my package manager to handle the archived js files

sudo pacman -S asar

In the developer console i discovered the js file path

In my pc the folder was

/opt/Notion/resources/app.asar

Made a backup

sudo cp app.asar app.asar.bak

Extracted the content with asar

sudo asar extract app.asar app
cd ./app

Inject the js script into the renderer/preload.js file
Then repack the app folder with asar

sudo asar pack ./app app.asar

and it should work! I choose preload.js randomly i think any js file in the source tab of the developer console should work.
Not a js developer by any means, just went with common sense, if i made any mistake let me now

[Kaspary]

The @dario-99 answer works for me!

I'm currently using Pop OS 22.04 (Ubuntu). To install the asar package, I use NPM with the following command:

npm install -g asar

Once it's installed, I proceed to unpack and pack the app.asar file. I prefer moving the app.asar to my user workspace, avoiding the need to configure my root user. After packing, I return the app.asar to notion path - /opt/Notion/resources/.

[hanshou101]

Inject the js script into the renderer/preload.js file Then repack the app folder with asar

sudo asar pack ./app app.asar

and it should work! I choose preload.js randomly i think any js file in the source tab of the developer console should work. Not a js developer by any means, just went with common sense, if i made any mistake let me now

@dario-99

Awesome Solution !

Brother, you accomplished what I always wanted to do. I have read a lot of Electron reverse analysis articles before, but I ignored 【the key details that are correctly used by you now】! Your solution filled my dead end and inspired me too!

[dario-99]

@hanshou101 Thanks!
Couldn't have done it without your previous discoveries, thank you so much for your contribution

[supermavster]

Thanks @dario-99 ;) it worked!

[archetyped]

Workaround works on MacOS as well.

Thanks @dario-99 and @hanshou101 for your contributions.

[dolikemedo]

Thank you very much @dario-99 , @hanshou101 !! :-)