Can't Repro
Status Update
Comments
dn...@google.com <dn...@google.com>
od...@gmail.com <od...@gmail.com> #3
[Empty comment from Monorail migration]
lb...@gmail.com <lb...@gmail.com> #4
Hey Paul, can you give input on how important this is?
dn...@google.com <dn...@google.com> #5
Doesn't this already exist? Or is this different from the manifest property?
lb...@gmail.com <lb...@gmail.com> #6
waiting on additional feedback.
lb...@gmail.com <lb...@gmail.com> #7
GitHub issue:
https://github.com/w3c/manifest/issues/737
Discussion doc (Google only):
https://docs.google.com/document/d/1wchuU6uZAt10LYYL4U0GmI4lndwdkoMdvXKLiZkJ5Aw/edit
#4:
> Doesn't this already exist? Or is this different from the manifest property?
There's been some confusion because this feature keeps being labeled as "display: browser", which does already exist and has a separate meaning (specifically, that the app is opened in a regular browser tab).
This feature is about having a standalone app window with multiple tabs (containing separate documents inside the app scope) inside it.
Regardless of how we design this, the name of the feature proposal should not be named after a proposed solution, since that unnecessarily pigeonholes us into a particular solution.
[Monorail components: UI>Browser>WebAppInstalls]
Discussion doc (Google only):
#4:
> Doesn't this already exist? Or is this different from the manifest property?
There's been some confusion because this feature keeps being labeled as "display: browser", which does already exist and has a separate meaning (specifically, that the app is opened in a regular browser tab).
This feature is about having a standalone app window with multiple tabs (containing separate documents inside the app scope) inside it.
Regardless of how we design this, the name of the feature proposal should not be named after a proposed solution, since that unnecessarily pigeonholes us into a particular solution.
[Monorail components: UI>Browser>WebAppInstalls]
Description
Version used:
compile 'com.android.support:appcompat-v7:23.2.0'
compile 'com.android.support:design:23.2.0'
Theme used:
default
Devices/Android versions reproduced on:
Nexus 5 with Android 6.0.1
- Relevant code to trigger the issue.
Just create a new project with the nav-drawer.
Then, play with the drawer.
- A screenrecord or screenshots showing the issue (if UI related).
Attached.
Also attached the project I've tested on.