[ZBX-7609] Frontend messaging close button does not stop alert sound Created: 2014 Jan 06  Updated: 2017 May 30  Resolved: 2014 Feb 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.10, 2.2.1
Fix Version/s: 2.0.11rc1, 2.2.2rc1, 2.3.0

Type: Incident report Priority: Trivial
Reporter: Kodai Terashima Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: globalmessages, sounds
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

Frontend messaging close button close messaging list, but does not stop alert sound. Sound will stop next screen refresh.

There is no way to stop sound if refresh period and Message timeout are long, and set Play sound to Mesage timeout.



 Comments   
Comment by Eduards Samersovs (Inactive) [ 2014 Jan 07 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7609

Comment by Ivo Kurzemnieks [ 2014 Jan 08 ]

(1) Related: pressing unmute, sound no longer continues to play.

Eduards Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7609-trunk

iivs CLOSED.

Comment by Ivo Kurzemnieks [ 2014 Jan 08 ]

(2) Let's remove those debugs at the beginning of each function.

Eduards Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7609-trunk

iivs CLOSED.

Comment by Ivo Kurzemnieks [ 2014 Jan 16 ]

(3) There are some problems in svn://svn.zabbix.com/branches/dev/ZBX-7609-trunk having at least two messages popping up. Affects mostly IE browsers and there is different and strange messaging behaviour in each one of them.

  • IE8, IE9 and IE10 higher severity message closes, but lower severity message stays on screen. After a while the screen is full of unclosed lower severity messages.
    IE8 and IE9 console error:
    'null' is null or not an object  jsLoader.php?ver=2.3.0&lang=en_US&showGuiMessaging=1,line 8134 character 4
  • IE10 sound stops after a while and lower severity messages don't close. Console error:
    SCRIPT5007: Unable to get property 'setAttribute' of undefined or null reference jSLoader.php, line 8134 character 4
  • IE11 first two messages don't close and there is no sound at all. Console error:
    MEDIA12899: AUDIO/VIDEO: Unknown MIME type.
  • Safari has no sound at all.

Note that this was tested with no page refresh used (for example in configuration pages)

Eduards RESOLVED in r.41647,41626. To play sound in Safari you need to install Apple QuickTime

iivs Downloading and installing quicktime solved sound playing problem for Safari.
Downloading and installing Silverlight solved sound playing problem for IE11.
Other IE versions tested and looks OK.

CLOSED.

Comment by Ivo Kurzemnieks [ 2014 Jan 16 ]

(4) There are some problems in svn://svn.zabbix.com/branches/dev/ZBX-7609 on various browsers having at least two messages popping up.

  • IE8, IE9, IE10, Chrome, Chromium, Opera, Safari and FF first two messages don't close. The messages that appear next, they do close, but two messages remain on screen at all times.
  • IE11 first two and sometimes four messages don't close and there is no sound at all. Console error:
    MEDIA12899: AUDIO/VIDEO: Unknown MIME type.
  • Safari first two messages don't close and there is no sound at all.

Note that this was tested with page no refresh used (for example in configuration pages)

Eduards This problems are the same as for (3), if we want we can integrate this changes also in 2.0, 2.2

iivs Tested again on 2.0 head revision and seems like this problem is was older and fix didn't make a regression for 2.0.

CLOSED.

Comment by Ivo Kurzemnieks [ 2014 Jan 22 ]

TESTED

Comment by Eduards Samersovs (Inactive) [ 2014 Jan 22 ]

Fixed in versions 2.3.0 (trunk) r.41753, 2.2.2rc1 r.41752, 2.0.11rc1 r.41750

Comment by richlv [ 2014 Feb 02 ]

(5) something's fishy with changelog entries.
trunk entry says "fixed frontend messages mute/unmute" and 2.0 entry says "fixed sound playing after frontend messages closing"

a) changelog entry for 2.2 is completely missing;
b) unless it's something only done in trunk, there shouldn't be trunk changelog entry;
c) was muting/unmuting not working properly not fixed in 2.0 & 2.2 ?
d) in trunk changelog this has been added in 'new features' section

Eduards RESOLVED

sasha Looks good! CLOSED

Generated at Fri Mar 29 10:03:43 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.