After some update of chrome or maybe moving my script to a new computer I am no longer able to use a very simple macro for sending the ↑ and ↓ arrow keys.
My code:
!w::send, {Up}
!s::send, {Down}
I attempted adding return to the end of the line and reformatting but only got the behaviour for ↓ regardless of combination. even more odd was that the following code also made the page scroll down
!w::send, {Up} return
and
!w::send, {NumpadUp} return
I am more than a little confused how such a simple macro is not functioning. in only google chrome but fine in other applications. My current thought is that it may overlap with some active extension but I am only seeing a possible conflict with a smooth scrolling extension that shares the usage of the alt key. This however was active last time the macro was functioning and worked to enable smooth scrolling. Attempts with the extension disabled have not produced different results.
I have also altered the key trigger to be just "w" and this yields no result in chrome. Yet the original code functions within text fields in chrome. I think this is mostly an issue with google chrome but I cannot understand why sending the key does not function despite it working when pressing the actual direction keys.
EDIT: So another round of troubleshooting I tried switching to a guest user and the macro functions. there must be an extension that is taking priority over the macro functions. What remains confusing that is it does not appear to have any relation to which key combination I attempt to trigger it with. I will have to start blank and progressively re-enable everything to find out more about the interaction.
Related
I have an HTML table with at most 25 columns (usually 5 or 6) and at most 25 rows. Each cell in the table contains a custom Web Component. These are minimal web components. For example, one wraps a number and you can set number formatting (e.g. format as currency) via the attributes. Another just displays a formatted string, etc. I am adding these components dynamically using appendChild on the td.
These Web Components are all using the Shadow DOM - as recommended in the documentation. So I create this simple table (6 rows and 25 columns) and I populate cells with these Web Components. If I do this in Chrome, my system crashes requiring a reboot (sometimes by forcing a shutdown). I tried this in Firefox, and the table renders in less than a second. Also I tried this in Edge and it crashes there too.
I tried re-doing my Web Components to remove the Shadow DOMs and voila, it works fine in Chrome and Firefox.
I don't want to do these component without the Shadow DOMs. Does anyone have any ideas?
Thanks
Update: this is still a problem. I tested in Edge browser and it does indeed work there (albeit a bit slow). Also tested in Safari/ MacOS and it works there too.
What a shame… I have to tell my users they can’t use Chrome and prevent the page from loading.
Update 9/2/2022: Without any changes to my code it is no longer an issue. The only explanation I have is that it might have been happily addressed by a scheduled Chrome update.
Now however, even though my table loads OK, if I open Developer Tools immediately after the table loads, I get a crash with error: 'Debugging Connection closed. Reason: Render process gone.'
Update 9/4/2022: I was overly optimistic about this error. I started testing my app again in Chrome today and the original problem still exists. I create my table in Chrome, interact with it in various ways (e.g. dynamically add a column, add an icon prefix to cell contents of a column, dynamically add a column with a drop-down menu in each cell, etc.) and eventually Chrome will crash.
I no longer expect this to be fixed. I logged a bug report with chromium.org and that is all I can do.
I think we can delete every element of a website from the inspector tool on chrome.
But here's the issue. I was using google calendar on chrome, and what i did was i added style="filter: invert(100%)" to the html container.
(I know it is silly to invert a website like that, but i was just testing some of my css)
After i did this, everything was inverted on the website, however a text "null" appeared on the top of the website:
Then, i searched for the null element, and tried to delete it, but the delete option itself is not there. I'm very confused, i have tried searching this on google and stack overflow itself, but no one seems to have the same problem as me :/
Can anyone offer some guidance?
I can delete it.
I think it has to do with the fact that Google continues to send the full status of the page as xhr internally at regular time intervals and receive responses for security and other reasons. As a result of this request, null is returned as a response and displayed on the screen.
I started using Google Script a few hours ago, and I noticed that the Autocompletion doesn't not work correctly. It activates when I press ; (semicolon), but not when I press . (period).
Logger. // Does not display anything
Logger; // Diplays clear(), getLog(), ...
I am using an french AZERTY keyboard and I noticed that when I switch a QUERTY keyboard, then it works correctly.
It makes everything hard to do because, first I do not have the autocomplete, and also it inserts a method at the end of the line every time I press Semicolon and Enter...
Does anyone knows why I have this problem or how to fix it ?
Thank you!
Posting this for documentation purposes.
This behaviour was reported in Issue Tracker a few weeks ago. Users who are experiencing this and want to keep track of this case might want to click the star on the top left in the referenced page.
Reference:
Issue Tracker: Autocompletion dialog malfunctions on AZERTY keyboards
I have a weird situation. One of my users is using functionality of Chrome (current version, 49, 50), that he drags and drops a file from his folder on local computer to normal input type=file button in a form on the webpage. Once again, let me stress it even more, its normal html input, no fancy javascript, no drag&drop events and handlers, nothing like this. It just takes the name of the dragged file and puts it into the input field, as like he selected it via "normal" way, opening the file select window, locating file on harddrive, selecting the file and confirming.
In some specific situation, this stops working (while doing some edits in the page via javascript / ajax), and I need to "reenable" it.
But, and that is my question, I haven't found any documentation of this "feature" in Google Chrome (or maybe some other browsers as well, I don't know). Why it works, how it works, how it should work and what to do if it stops working :) Does anyone has any experience with this ? The only way how to "fix" it now is to reload the page. I'd love to solve it ... :)
EDIT 1 : I just did a quick test, it works and bugs the same way in Firefox on Win. It doesn't show any error in dev console or any message, it just doesn't add the file as expected.
I've found it. The previous discussion with deceze pointed me to test the javascripts I have on the page, that do not "interfere" with the input type=file ... they weren't any such scripts, but I've found that after doubleclick on the table (that I'm using for editing) this script is being called
$(document).bind('drop dragover', function (e) {
e.preventDefault();
});
and there wasn't any unbind action when table is saved ... this caused the drag and drop everywhere on the page to stop working after the edit.
this is insanely annoying problem:
AS3 full screen application based on ADOBE FLEX 4, text field. User types something in text field, and then starts clicking backspace many many times to remove what he just wrote, and for some reason, instead of removing characters from text field it tells browser to GO BACK and user navigates away. Why?! Please, please help, this is so terrible. My users are losing important unsaved this is data while using my application!
i am using safari browser
PLEASE HELP.
Wow, this is terrible, I am so irritated, it happens every single time
It is possible that the focus is lost from your text field when hitting the backspace multiple times (check if you are firing some events on the text field that may cause this), which causes the main window to take focus and trigger 'Back' on the browser.
The root of the problem is that the browser carries out keyboard shortcuts REGARDLESS of the flash app having the focus or not. From what I heard this problem does not exist on Safari's for Mac, only Safari for Windows.
I would check to see what browser you are in and then create a popup saying you this app does NOT work on Safari browser ON windows.
Scratching head*
Well maybe if HAD to solve this, I would use the ExternalInterface to interact with Safari or javascript to PREVENT the history back button from getting applied. So it won't go back to an old page. That is what I would look into.