New attribute header_image_expanded supplies background image.
Reviewed with Leyla (last commit too)

EXT-2241 layout of Preferences > Sound needs to be improved for I18N, EXT-2276 Advanced water settings floater sliders spaced too tight

When the amount of the texture that's being drawn by the plugin shrinks in either width or height, reallocate the texture (which clears it).

Font and color can be set in accordion_tab.xml

Media focus is still tracked separately from LLSelectMgr (which was a change made during a refactor a while ago), but LLViewerMediaFocus now keeps LLSelectMgr updated with the current media focus when it changes.

Added a special case for media focus to LLSelectMgr::deselectAllIfTooFar(), since it was making the focus ring not show up when media focus was on distant media.

Otherwise it discards a typed line in progress.

Normally LL_ERRS in a developer build of the viewer pops up an OS message box
with the text of the LL_ERRS log message, requiring user intervention to
proceed. This isn't good for unattended testing, especially on Parabuild
machines. Running the viewer with '--set QAModeTermCode n' for some
0 < n < 256 will, on LL_ERRS, cause the viewer to terminate immediately with
_exit(n).

See Communications Spec for design.  Arrow keys still move you if text chat field
is empty.  Also fixed ctrl-up/ctrl-down for recently chatted lines.
Reviewed with Richard.

reviewed by James

EXT-2160 texture picker cancel button should be on the right, General texture and color picker cleanup

http://jira.secondlife.com/browse/EXT-2138

--HG--
branch : product-engine

http://jira.secondlife.com/browse/EXT-2172

FIX DEV-42115: Remove modify permission check that would grant navigate/interact or controls "permission"
Review #27

Back when media controls (an unfortunately much-overloaded word) was called media permission (also an overloaded word), we granted "permission" for interact/navigate or controls "display" if the requestor agent had modify permissions. This decision doesn't seem to make sense, because it is a common use case to want to "disable" controls (or perhaps interaction/navigate) even for the user who created the object (i.e. who has modify permissions). This removes that check.

NOTE that this check is also made on the server, but in that case modify permissions *grants* the right to navigate in that case. Although the code is very similar, the viewer version is trying to address a use case story, whereas the other is trying to prevent a griefing vector.

--HG--
branch : product-engine

http://jira.secondlife.com/browse/EXT-2218

--HG--
branch : product-engine

--HG--
branch : product-engine