@@ -27,7 +27,6 @@ Ionic...) nor Chrome extensions.
27
27
4 . [ Customization] ( #customizing-firebaseui-for-authentication )
28
28
5 . [ Advanced] ( #advanced )
29
29
6 . [ Known issues] ( #known-issues )
30
- 7 . [ Release Notes] ( #release-notes )
31
30
32
31
## Installation
33
32
@@ -73,6 +72,10 @@ object.
73
72
74
73
The following example shows how to set up a sign-in screen with all supported providers.
75
74
75
+ > We recommend opening the widget in a popup window or redirecting to it, as a
76
+ > [ known issue with single page applications] ( #web-single-page-applications-are-not-fully-supported )
77
+ > may lead to a rendering bug.
78
+
76
79
``` html
77
80
<!DOCTYPE html>
78
81
<html >
@@ -332,21 +335,9 @@ When a user has enabled the private browsing mode in Safari, the web storage is
332
335
currently results in an error being thrown upon Firebase Auth initialization. Therefore, when
333
336
following the snippets above, FirebaseUI will never get initialized and no UI will be displayed.
334
337
335
- ### Tips for Single Page apps ( ` UI Widget is already rendered on the page ` error)
338
+ ### Web Single Page Applications are not fully supported
336
339
337
340
When re-rendering the FirebaseUI Auth widget (for instance after signing in a user, signing her out
338
341
and trying to sign her in again), it will fail with an `Uncaught Error: UI Widget is already
339
- rendered on the page. Only one widget instance can be rendered per page. Reset the previous instance
340
- before rendering a new one.` error. You can use the ` reset()` method when removing the widget to
341
- make sure you can draw it again.
342
-
343
- ## Release Notes
344
-
345
- ### 0.5
346
-
347
- - FirebaseUI now supports Single Page Application: a ` reset ` method was added to allow to dispose
348
- of the widget. When the user leaves a page where the FirebaseUI widget was rendered (for instance
349
- in a ` componentWillUnmount ` in a React component), call the ` reset ` method of the
350
- ` firebaseui.auth.AuthUI ` instance you created. Also, call the ` reset ` method before rendering
351
- again the widget if any has already been rendered on the page. Please refer to the demo for guidance
352
- on how to use FirebaseUI in a Single Page Application context.
342
+ initialized on the page. Only one widget instance can be initialized per page.` error. We recommend
343
+ using the widget in a popup window or redirecting to it while we work on a fix for this issue.
0 commit comments