web browser - fullscreen from code - browser

I read many post on the subject but there is no concrete answer I found: is it possible to trigger F11 on internet browsers or somehow make browser to go into full screen? there are a lot of workarounds, but none of them are real full screen.
Thanks

Because you didn't specify the OS (and if the webbrowser is embedded) i can only give you this answer.
You can send a key with a sendkeys 'interface', it emulates a keypress, for example 'F11'.
More info: google sendkeys
Maybe this answer can lead you into the right direction.

Related

Some Gmail Keyboard Shortcuts are not working properly with non-US keyboard

I am using a non-US keyboard (Brazilian ABNT2), and some keyboard shortcuts are not working specifically in Gmail running on Windows.
But the same keyboard shortcuts work properly in Gmail running on MacOS.
And also the same keyboard shortcuts work properly in Google Calendar, both in Windows and MacOS.
It seems to be only a Gmail+Windows issue.
I can't use shortcuts with "/" and "" on my Brazilian ABNT2 keyboard, an I believe it's because these keys have a different code/mapping than the same keys in an International-US keyboard:
International-US:
[/ ?] = Key 0x0035 (00_35)
[\ |] = Key 0x002B (00_2B)
ABNT2:
[\ |] = Key 0x0056 (00_56)
[/ ?] = Key: 0x0073 (00_73)
For some reason, these keys produce the correct effect when writing an email. No issues in writing.
But the problem happens when they are used as keyboard shortcuts.
Being more specific with examples, on an ABNT2 keyboard on Gmail+Windows 10:
pressing "?" key does nothing (and should open the Gmail help);
pressing "/" key does nothing (and should move the focus to the search box);
pressing "\" sequence of keys does nothing (and as per my personally configured keyboard shortcuts, should archive the selected email).
Complement 1: These issues are not affecting gmail in my MacOS (everything works properly there). This is happening only in my Windows 10.
Complement 2: this issue is not affecting Google Calendar on Windows 10... Pressing "/" correctly moves the focus to the search box, both in MacOS and Windows 10. So it's clearly some problem in Gmail, not in the hardware.
Any ideas on how I could make these exact keyboard shortcuts to work in Gmail on Windows 10?
Is this a bug, and if yes, is there anyone from Google here that can help to address this issue to be corrected?
Thanks in advance for your reply!
By your description it seems or an hardware issue or some settings in the Gmail account.
Have you checked if the setting for the shortcuts is actually on?
On a computer, go to Gmail.
In the top right, click Settings and then ‘See all settings.’
Click Settings.
Scroll down to the "Keyboard shortcuts" section.
Select Keyboard shortcuts on.
At the bottom of the page, click Save Changes.
Keyboard shortcuts for Gmail: https://support.google.com/mail/answer/6594
If is not this then I suggest you to do some testing with your hardware.
I tell you this because by experience this doesn't seems like a bug at all for the simple reason that in a Mac works but in a windows it doesn't. Also it is very unlikely that there may be some discrepancy between the gmail web UI and a OS, but rather between the gmail UI and the browser firstly.
Actually by putting in order what you should check first:
Hardware, check by changing the keyboard language in the windows system ---> Switch between languages using the Language bar: https://support.microsoft.com/en-us/office/switch-between-languages-using-the-language-bar-1c2242c0-fe15-4bc3-99bc-535de6f4f258
.2 If doesn't help try on a different Windows computer and with a different Keyboard.
.3 If still not working then use a different Browser (is the browser that is interacting with the webpage, in this case gmail.google.com and not the device OS directly with Gmail).
If then you see then is not solving you may report this by going in the top right corner in gmail.google.com, press the question mark (?) logo and leave a feedback as it would be the best way to directly comunicate with a Googler.

Open webpage in full screen in running sketch at Processing

I wonder how I open webpage in full screen mode in running sketch at Processing.
I am making a simple question/answer game but before solving question. I want users to register or login website first. And then when pressed a certain button on webpage it brings back to start to question.
I appreciate any suggestions.
The answer to this is going to depend on exactly what you're trying to do.
Are you trying to do this from Java mode? If so, google something like "java launch webpage".
Are you trying to do this from JavaScript mode, or with Processing.js or p5.js? If so, google something like "JavaScript fullscreen" and you'll find examples like this and this.
That will allow you to open a webapge in fullscreen mode. Then going back to your Processing sketch again depends on whether you're using Java or JavaScript.
If you're using Java, this is going to be pretty difficult, as you aren't going to be able to get events from the webpage to your Java code. You could try using an applet, but I wouldn't really recommend that since applets are pretty much dead anyway.
If you're using JavaScript, then it's a little easier. You can simply detect the button click in the webpage (by adding an onclick callback) and then call whatever functions you want to close the webpage and reactivate your Processing sketch.
It's hard to answer general "how do I do this" type questions. Stack Overflow is more designed for specific "I tried X, expected Y, but got Z instead" type questions. I really recommend that you just try something out and post an MCVE showing exactly where you're stuck. Good luck.

PyQt: Simulate real mouse click on "desktop"?

If there's any way to simulate a real mouse click (press + release) at the absolute position of current desktop with PyQt, without other extenal library like PyUserInput?
I search around and just found this and this. But If I don't misunderstand, they seem to send their click event to Qt application it self, instead of the desktop?
Use PyQt's QTest, together with unittest or such. See also for example http://www.voom.net/pyqt-qtest-example.
If this is not for unit testing, look at sendEvent and postEvent (See http://doc.qt.digia.com/qq/qq11-events.html#syntheticevents). There are some limitations to Qt's mechanism for generating "artificial" events but based on what you describe, it is likely to work. If you have tried those and it doesn't work, please post the code you tried.

Sahi: Cannot execute scripts recorded in a browser in multiple browsers

Our web application is designed such that the text transform is picked from CSS.
There are multiple links on a webpage; hence i will take example of a Next link.
When i hover the mouse over Next link in FF, it shows the below code:
_click(_link("Next"));
Similarly when i hover the mouse over the same link in Chrome, it shows the below code:
_click(_link("NEXT"));
When the script is recorded in FF and executed in chrome, it fails at the location because "Next" link is unavailable. This is one example of a link and there are multiple links and multiple pages. For this scenario, do i need to verify the text for each link or is there a universal way i.e. toLowercase method that can help me.
Thanks.
As Kshitij pointed out, you can get this working by using a regular expression as your accessor... but you might also check the Alternatives pulldown in the Controller. Perhaps there's an alternative accessor that is better suited for both browsers.
I think, the question should be how can Sahi identify the element with text by ignoring the case-sensitivity.
Any tool can only record the attributes which is available on the browser at that time.
You can use the following code to achieve the functionality:
_click(_link("/Next/i"));

Is it ok not to have a button for a search box?

I was wondering if it was ever ok not to have a submit button (Ok, Go or Search for example) near a search box in Web pages.
I know that hitting enter is much faster and that it will perform the search.
However, is it an accepted convention for the average non tech savvy user or only for the tech community?
For example, the search box here at stackoverflow doesn't have a submit button, but I don't think anyone is complaining (and I sure don't).
On the other hand, someone suggested using Google as an example: would people notice if the buttons were removed?
I just started reading Don't Make Me Think by Steve Krug and he mentions that every search box should have something that tells me I can click on it to launch the search.
Your thoughts?
Why you should have a button:
Not everyone knows they can hit
enter, so you are leaving some less
savvy people out in the cold.
Some devices like phones and consoles may not have a way to submit without a button. The PC based browser is still dominant but don't assume it is the only way people access your site.
You may not have a button if (both conditions must be satisfied):
Your audience is tech savvy (as on SO)
You provide a visual cue that the search box actually is a search box
By adding text inside it mentioning it should be used to search
By adding an icon inside the box
Generally I would think that hitting enter is a shortcut to submit rather than the primary means.
I think it depends on your target market. If you are StackOverflow it's not too hard too think they know how to use a browser (using a back button on a browser to navigate is a similair design convention) and pressing Enter = submit for search.
However if your target market is say mechanics (no offence to mechanics) that don't use a browser/computer often then look at how Google does it (and they target the broadest scope) - they have a button to submit.
There is a middle ground you could look at, which is have a water mark like StackOverflow which tells users "Click here, type in search values and press enter to search" - or something like that (hopefully shorter) where you actually catering for users of all levels.
Whether or not a button is required depends on the audience. Here are issues to consider:
Technically oriented users may not need a button and will usually not have to think about hitting enter to submit a search request.
Conversely non-technical people may not even know it is possible to hit enter to submit a search request. So no amount of thinking might work for them.
There may be technology limitations that require a button. If you expect your audience to be browsing your form from a platform that does not provide an implicit way to submit a search request then you may need to provide an explicit button.
So essentially you need to know your audiences and determine where the edge cases lie and how critical they are. Using SO as an example, it is directed at technical users so an explicit button probably isn't required. However for a site like google where you need to be accessible to every single user using every possible platform, a clear explicit search button is a must.
"Don't Make Me Think" - so gimme a button.
There will always be someone using the application for the first time; don't make them think either. And your screen shouldn't be so fussy that it is impossible to fit the button in comfortably - that would indicate a different set of problems.
I think for a non-tech person some sort of submit button is needed. Think about people who don't use computers very much. They often click all of the buttons needed instead of hitting enter because they don't realize enter does the same thing. My opinion...if it isn't for tech guys only then it should be as simple as possible.
It depends on your audience. Steve's audience is everybody. Majority of which are so far from IT you'd need a telescope to see them. If your auditory is a single user, you might skip all clues: button (with or w/o names), in-box label.
For my own login window I leave two fields: no labels, no buttons, no javascript to tell you which one is which. But that's not a public project.
A while ago there was an article on Smashing Magazine about this.
There were some alternatives like a looking glass or another icon, but basically there is always a button, or something which represents it.
Having a button makes it clearer that the text field is a search field. Merely having the text field itself indicate this in its contents is unsufficient.

Resources