HZN-956: Implement browser notification

[fooker]

• JIRA: http://issues.opennms.org/browse/HZN-956

[fooker]

@indigo423 suggested to use a more modern/flat logo instead of https://github.com/OpenNMS/opennms/blob/5f4ae13ccef1ff185c49595e41ca15449283b6fb/opennms-webapp/src/main/webapp/images/o-192.png. Thoughts?

[indigo423]

@indigo423 suggested to use a more modern/flat logo instead of https://github.com/OpenNMS/opennms/blob/5f4ae13ccef1ff185c49595e41ca15449283b6fb/opennms-webapp/src/main/webapp/images/o-192.png. Thoughts?

Updated so it uses the new o-logo

[fooker]

Mentioned in whatsnew

[indigo423]

I did a functional test and got it to work with Safari, Chrome and Firefox. 👍 from me.

[pbrane]

I tested as well. Works for me w/Safari. How difficult would it be to make the notification a clickable reference back to the notification in the browser such that the user could ack the notification?

[pbrane]

Pretty cool!

[indigo423]

I tested as well. Works for me w/Safari. How difficult would it be to make the notification a clickable reference back to the notification in the browser such that the user could ack the notification?

I tried this but but they get encoded and are not interpreted as HTML links. I can imagine the base href can be unknown to opennms itself e.g. behind proxy and the opennms jetty property opennms.web.base-url = https://%x%c/

[pbrane]

Bummer.

[fooker]

How difficult would it be to make the notification a clickable reference back to the notification in the browser such that the user could ack the notification?

I've already looked into it. There is some support for "actions". But it's still beta and not supported by most stable browsers. It also requires HTTPS and a lot of changes to the authentication handling. Maybe later...

[j-white]

Awesome. Thanks.

[indigo423]

@fooker what means your commit message:

HZN-956: Migrated js to asserts

😄