Good, I'm sure you can get this to work.
I have to say something about web browsers, which is where most unsuspecting wide gamut display owners trip up. At the moment there is only one browser that works satisfactorily with wide gamut displays, and that's Firefox. But you still have to modify the default configuration a bit.
Several browsers claim to be color managed, including Safari. The problem is that most content on the web is untagged (doesn't have an embedded profile), and that breaks the color management chain. There's no source profile to convert to the monitor profile from, and so those browsers just leave the material in an unmanaged state, sending the image RGB numbers straight through to the display unmodified.
Firefox has an optional configuration that assigns sRGB to any untagged material. This gets the color management machine running again. Assigning sRGB is a safe assumption since it's most likely created in sRGB with that intent. And this has the added advantage that you effectively get full color management even on untagged material, instead of "close enough" which is what you normally get.
To get there, type about:config (copy/paste that) into the address bar, and scroll down to gfx.color_management.mode. Change the value from 2 to 1, and relaunch Firefox. The beauty of this setting is that it affects the whole works, page elements as well as images. Everything appears correctly.
(and while you're there, you can enable v4 monitor profiles as well, in case you should ever need that).