I am getting this banner while using the chrome.debugger APIs. Earlier it was hidden if "--silent-debugger-extension-api" flag was used but from Chrome version 100 and above the flag is not working as expected.
Is there any other workaround to hide the banner?
Please see the attached image for more details.
Tried using "--silent-debugger-extension-api" flag
Also tried dispatchEvent apis to simulate the keystrokes but it didn't work as expected
Same here as #wOxxOm has said. You have to close all the instances to get the flag to work. As a workaround, I suppose you can use other release channels like Beta, Dev and Canary, then you won't have to close the main window of the Stable channel.
[![][1]][1]
Hi! When switched to legacy editor this screen showed up and it makes impossible to switch back to new version as inactive button. I did sign off and sign in, it does not help. Any ideas how to get back to new editor?
[1]: https://i.stack.imgur.com/rz7Rp.png
What you are describing might in fact be a bug.
You may want to check this issue here on Google's Issue Tracker.
I suggest you star the issue here and eventually add a comment saying that you are affected by it.
I have a special listbox that I could automate best by sending a down arrow and pressing enter.
I can press enter like so:
listbox_example = find(input, "listbox-example")
listbox-example.set("stuff")
#down arrow command goes here
listbox-example.native.send_keys :return
How do I write the down arrow command?
If I remember correctly the correct way to send the down arrow command is to use arrow_down
So your code should look like this
listbox-example.native.sendkeys :arrow_down
If you would like a list of all the available keys that you can send, then docs are your friend here
http://www.ruby-doc.org/gems/docs/f/frameworks-capybara-0.2.18/SendKeys.html
EDIT: This link might have the intended content.
https://www.omniref.com/ruby/gems/frameworks-capybara/0.2.18/symbols/SendKeys
find('#element_id').send_keys :arrow_down
These answers are dependent on the driver I believe. I am using the Apparition js driver (i.e., it's a plugin for capybara) and the magic code that works is this:
find("input[type='search']").send_keys(:down).send_keys(:enter)
Using Capybara 3.33.0
Using the Apparition JS driver (plugin for capybara) version 0.6.0
These days (Capybara version 2.5+) you can simulate <enter> key in the following way:
find('.selector').set("text\n")
The \n is key here. I think you should be able to simulate down arrow in a very similar way.
I added an extra parameter to Chrome "--disable-web-security". After I add this the "same origin policy" gets disabled which is exactly what I want.
The problem is that when I start Chrome an yellow information bar appears at the top and says:
"You are using and unsupported command-line flag: --disable-web-security. Stability and security will suffer."
The weird thing is that the flag seems to be supported as I tested Chrome with and without it.
My question is: Can that information bar be disabled with another flag or any other way ?
Thanks in advance
Try going to about:flags in the address bar and disabling Native Client..
I currently have a webpage serving up phone numbers, some of these phone numbers have extensions so I have written the HTML like this:
+44-1234-56788 / <a href="tel:+44-1234-567;ext=99">+44-1234-56799</a
When I hit this page in my Android browser and tap one of the phone numbers, it loads up in my phone dialer (UK Samsung Galaxy s2 stock) as:
+44-1234-567;ext=88
which I don't think is correct. Surely it should omit the ;ext= word.
Have I misread the RFC for implementing tel?
Seems the proper way to do it is use a comma:
+44-1234-567 ext.88
Just tested with iPhone and Android OS 2.1. Using ;ext=88 converts the ext bit into a number that is dialed with the extension (so it dials something like 35888 instead of 88).
Comment for How do I include extensions in the tel: URI?
As of June 2021 the RFC3966 ;ext= syntax still isn't implemented by Android, and it's inelegantly implemented by iOS.
Using ;ext=123 as an example:
Android: after the call connects a modal window appears asking Send the following tones? 396123 with No and Yes buttons. "Send the following tones?" is a precise technical description of what will happen if the user taps Yes, but it is probably not the best wording for the average user.
Android converts ;ext=123 into 396123 because it treats the letters the same way as if you were dialing something like 1-800-FLOWERS, and this is a broken implementation of the syntax.
iOS provides an option to the left of the Disconnect button that says Dial “ext=…”. When you tap on this "button" it will dial the extension number. This is inelegant and has bad usability because the "button" doesn't look like a button — it's just plain text — and because you can't see the extension number.
In addition, when you first tap on a phone link in iOS it presents a button at the bottom of the screen which partially rewrites the phone number into a local format, but which also preserves most of the ;ext= syntax, e.g. Call +1 (555) 555-5555;ext123. This is also inelegant, and it's ugly besides.
If you instead use just a ; which is supposed to mean "wait," as in "wait until the auto attendant message ends and then automatically dial the extension":
iOS: tapping the link displays a button stating Call +1 (555) 555-5555;123 which is slightly less ugly than the button described above.
iOs provides the same extension-dialing "button" described above except the extension number is visible, e.g. Dial “123”. It still has the other usability problems.
iOS does not automatically dial the extension after the message ends.
Android: after the call connects a modal window appears asking Send the following tones? 123 with No and Yes buttons.
Android does not automatically dial the extension after the message ends.
So for now, as of June 2021 it seems that the only way to include extensions in tel: links that will actually work is to use either ; for "wait" or , for "pause":
555-555-5555 ext. 123 — this will provide a UI component which the user can invoke to dial the extension. The usability of the UI component depends on the OS; neither are great, but Android's is arguably better.
555-555-5555 ext. 123 — this will automatically dial the extension a couple seconds after the call connects. Note: This mechanism will not work with voicemail systems that don't accept user input until the auto attendant message ends.
According to the documentation, you can add what you want like so 12345678;ext=123
See RFC 3966
In all the examples I saw, the value of ext is contained in the full number. So try including 88 in the href value:
+44-1234-56788
For those still wondering about this problem: I've found it best to use this format:
<a href="tel:+13235798328;22">
Standards at thenewcode from 3 months ago suggest using a microdata pause.
<a href="tel:+13235798328p22">
Related:
Different standards persist across different external platforms and may change the processing of URIs. Click to call
features on Google Developers docs do not specify
Example:
Office's Skype uses x to represent extension within skype.
I feel like this is kind of a cop-out answer, but if this is not implemented consistently across devices yet, probably best to just not include the extension and let people dial it by hand:
+44-1234-567 ext. 88
or
+44-1234-567 ext. 88
Better to make the user do more work than to send 1/2 your users to the wrong extension.
I don't get the answers to this question - I think the're wrong. The correct link would look like this:
+44-1234-567 ext. 88