You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2017. It is now read-only.
Does the issue occur in "quirks mode", "standards mode" or both? If you
don't know, does your HTML page contains a DOCTYPE declaration?
Yes, contains DOCTYPE declaration.
What version of GWT are you using? 1.4.60? 2.0.4? Other?
2.3.3
What version of the gwt-voices jar file or library file are you using?
2.1.2
What operating system(s) are you using? Windows? Linux? Mac?
Windows
Does the issue occur in web mode, development mode (formerly "hosted
mode"), both or don't know?
both
What browser(s) do you use? Chrome, Firefox, IE, Safari, other?
Chrome
What is the browser version (if you know) from Help->About?
14.0
What steps will reproduce the problem? Please attach sample code if you
can.
1. Create a new sound controller using:
private static SoundController soundController = new SoundController();
2. Create a new sound using:
private static Sound msgSound =
soundController.createSound(Sound.MIME_TYPE_AUDIO_BASIC,
GWT.getModuleBaseURL()+"sound/msg.wav");
3.Play the sound using msgSound.play();
What is the expected output? What do you see instead?
I expect the sound to play, which it does, but on my current page the focus
will be lost from whatever element that I currently have the focus on. For
instance if I have the cursor in a text box on the page and the sound is
played, I hear the sound, but the cursor is no longer in my text box. Somehow
when the sound is played it takes the cursor focus to some unknown place.
Do you have a workaround?
Only workaround is to not play the sound.
Please provide any additional information below.
Original issue reported on code.google.com by [email protected] on 5 Oct 2011 at 4:22
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 5 Oct 2011 at 4:22The text was updated successfully, but these errors were encountered: