#33856: Django 4 Giant Enormous Bug Report
-------------------------------------+-------------------------------------
     Reporter:  DADIDADISUPERDADI    |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  HTTP handling        |                  Version:  4.0
     Severity:  Release blocker      |               Resolution:
     Keywords:  Safari, Backbutton,  |             Triage Stage:
  Django4                            |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by DADIDADISUPERDADI:

Old description:

> ug description: Page A is accessed directly, Click something on page A
> goes to page B, Press back button back to Page A, And simple html
> elements on Page A will stop working with Safari.
>
> See the bug live at: https://howtoback.com/
>
> Django 3 no such bug
>
> The bug has been proven, Given how big the iPhone market is, Thus the
> gravity of this bug, I feel obligated to inform the community
>
> How IOS 15 Backbutton works in a nutshell, onclick="history.back();" Very
> sloppy for a trillion dollar company's browser, FYI this bug only happens
> in https not http, Let me know if the Django dev team knows what's in
> Django 4+ causing this bug.

New description:

 Bug description: Page A is accessed directly, Click something on page A
 goes to page B, Press back button back to Page A, And simple html elements
 on Page A will stop working with Safari.

 See the bug live at: https://howtoback.com/

 Django 3 no such bug

 The bug has been proven, Given how big the iPhone market is, Thus the
 gravity of this bug, I feel obligated to report this bug

 How IOS 15 Backbutton works in a nutshell, onclick="history.back();" Very
 sloppy for a trillion dollar company's browser, FYI this bug only happens
 in https not http, Let me know if the Django dev team knows what's in
 Django 4+ causing this bug.

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33856#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018211872cda-15b99f9c-df54-4268-9bc7-72d5596bf2ce-000000%40eu-central-1.amazonses.com.

Reply via email to