Fastboot does not respect `rootElement`
See original GitHub issueIf rootElement
is defined in an application, both the fastboot HTML and the Ember DOM are rendered.
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
fastboot doesn't see device
One thing I don't understand is why adb saw device and fastboot not. ... Scenario: the device is visible with adb devices but...
Read more >fastboot cannot recognize device but adb can - XDA Forums
I ran adb reboot bootloader from pc to boot phone into fastboot. In the bootloader it states device state is unlocked. However fastboot...
Read more >Android Fastboot devices not returning device - Stack Overflow
For Windows: Open device manager; Find Unknown "Android" device (likely listed under Other devices with an exclamation mark); Update driver ...
Read more >Fix Fastboot/Adb & Qualcomm drivers (Unbrick tool ... - YouTube
If you want to root your Android phone, unlock the bootloader, ... Fix Fastboot / Adb & Qualcomm drivers (Unbrick tool) not detecting...
Read more >Fastboot Not Detecting Device on Windows 10 - Beebom
If Fastboot is not detecting devices on Windows 10/11, follow our guide and install the fastboot drivers for OnePlus, Xiaomi, Realme & more....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m strangely seeing the double render suddenly in the opposite case, where the rootElement is not set…and if I set it to an arbitrary value, the double rendering stops 😶
I noticed in my package.lock that ember-cli-fastboot had upgraded automatically during my last npm install from
1.1.1
to1.1.3
and fastboot itself correspondingly from1.1.2
to1.1.3
since my package.json had ember-cli-fastboot set to^1.1.1
.Changing my package.json for ember-cli-fastboot to stay at
1.1.1
and reinstalling dependencies also resolved the double rendering without having to set an arbitrary rootElement, so the bug seems to have been produced during one of the above version changes.Is this fixed as of this commit since it clears out everything in the
<body>
tag? https://github.com/ember-fastboot/ember-cli-fastboot/pull/569/files