Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Slipped Oct iteration. We... don't really have a plan here yet, but this is P1 to stop the bleeding.
libraries where all resources are currently considered public but have never been tracked
Safest route for external developers is to make all existing resources officially public. That's going to be more work since we can't just copy the public.txt file. It also means that internal developers are locked into their existing resources, which is... safer, but not good for evolution of libraries.
Easiest route for internal developers (and our team) is to make all existing resources officially private. That will potentially break g3 drops and third-party libraries; however, it's an easy workaround given that we don't do resource namespacing yet. Developers can just define the resource that they (or their dependency) needs. Anyone using a dependency's R class directly is already hosed, anyway, so we'll ignore that.
jb...@google.com
Going to move forward with "fixing" the libraries which accidentally exposed all their resources as public.
Tentatively, we'll:
- Require a
public.txtto exist in the AAR, with a failure message along the lines of "At least one public resource must be defined. If your library has no public resources then please define a single, empty<public />element inres/values/public.xml." - Add a
public.xmlfile as described to all failing libraries - Be very, very explicit about the change in release notes
- Deal with the fallout in g3
Estimate is 2 due to g3 issues.
Description
I have a DialogFragment that opens another DialogFragment as a child. When you rotate the screen, and the dialogs are recreated, the windows are shown in the wrong order (the parent on top of the child, focused - you cannot interact with the child as tapping outside the parent will close both).
This only happens if the second DialogFragment does not override onCreateView (instead using e.g. an AlertDialog as in my sample). If you do override onCreateView, as long as you don't return null, the dialogs will be recreated in the right order. In my sample you can see a TODO where you can uncomment the function in order to fix the issue.
I am attaching a sample project illustrating the issue and two screenshots.
Expected: regardless of what is returned from onCreateView, the two dialog's windows should be recreated in the same order as they were before rotation.