New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 715657 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature
Proj-XR



Sign in to add a comment

Add drop shadow (border) to WebVR security warnings

Project Member Reported by cjgrant@chromium.org, Apr 26 2017

Issue description

In the HTML UI, the permanent and transient security warnings had feathered dark edges to visually separate them from content.  The same should be implemented in the natively-rendered equivalent.

See the v0 UX specs, but also note that klausw@ had obtained security sign-off on the original appearance, so we should match those as closely as possible.

This is follow-on work to crbug/713779.
 
Components: Blink>WebVR
Labels: -VR-BBB M-60
Status: Available (was: Untriaged)
Labels: -M-60
Labels: -Pri-1 Pri-2
Is this still an issue?
There is still no drop shadow.  However, there are other UI elements to which a drop shadow may also now be applied.

Ian started an exploratory CL to allow arbitrary rounded corners on UI elements, via shader rather than texture.  We should consider doing the same thing for drop shadow, as the textures themselves don't much care if they have a drop shadow or not.

Components: -UI>Browser>VR Internals>VR
Labels: VR-Triage-Close
We're also going to be redesigning toast UI, which the WebVR security warning will inherit, and the new approach may not use drop shadows. Can close this for now.
Status: Archived (was: Available)
Closing this bug via bulk-edit.  This bug tracks future work that is not yet scoped.  For maintainability, we are now tracking aspirational future work here:

http://go/chrome-vr-backlog

In the future, this bug may be re-opened when in scope, or replaced by a new bug if warranted.

Comment 9 by bshe@chromium.org, Nov 27 2017

Cc: vollick@chromium.org
+vollick, with the new awesome shadow element that you introduced recently, is this a somewhat trivial fix now? If so, we could perhaps reopen this bug?
Yep, I think this would be pretty straightforward.
Components: Internals>XR
Components: Blink>WebXR

Sign in to add a comment