Closed Bug 1168479 Opened 9 years ago Closed 9 years ago

[UX] Design a treatment for handling automatic https redirect from http version of site

Categories

(Firefox :: General, defect, P1)

Product:
Firefox
Component:
General
Type:
defect
Points:
5

Tracking

()

Status:
RESOLVED FIXED
Iteration:
41.2 - Jun 8
Tracking Flags:
Tracking Status
firefox41 --- affected

People

(Reporter: agrigas, Assigned: agrigas)

References

Details

(Whiteboard: [fxprivacy] [ux])

User Story

If a user has previously visited a site via https and types in the domain into the awesome bar, automatically re-direct them to the secure version of the site (https).

Attachments

(1 file, 3 obsolete files)

https only.png
397.53 KB, image/png
phlsa
: ui-review+
Details 
Add a control for users to connect via https if they've previously visited a site over https or if we know that an https site exists and they are on a http site.
Flags: firefox-backlog?
Summary: [UX] Design for https control within control center → [UX] Create a design for https control within control center
Hi Aislinn, can you provide a point value.
Status: NEW → ASSIGNED
Iteration: --- → 41.2 - Jun 8
Flags: qe-verify-
Flags: needinfo?(agrigas)
Flags: firefox-backlog?
Flags: firefox-backlog+
Whiteboard: [fxprivacy] → [fxprivacy] [ux]
Blocks: 1169134
(In reply to Marco Mucci [:MarcoM] from comment #1)
> Hi Aislinn, can you provide a point value.

5
Flags: needinfo?(agrigas)
Points: --- → 5
Priority: -- → P1
Summary: [UX] Create a design for https control within control center → [UX] Design a treatment for handling automatic https redirect from http version of site
User Story: (updated)
Attached image https redirect .png (obsolete) — 

    
  

        Attachment #8613514 -
        Flags: ui-review?(philipp)

    
    

    
  

      
      
      
      

        Attached image
          
        https.png (obsolete)
        — 
      

    


  

        Attachment #8613514 -
        Attachment is obsolete: true

        Attachment #8613514 -
        Flags: ui-review?(philipp)

        Attachment #8614035 -
        Flags: ui-review?(philipp)

    
    

    
  

      
      
      
      

        Attached image
          
        http.png (obsolete)
        — 
      

    


  

        Attachment #8614036 -
        Flags: ui-review?(philipp)

    
    

    
  

      
      
      
      

        Attached image
          
        https only.png
        — 
      

    


  
revision to only handle awesome bar auto-redirect with no visible notification/ui change

        Attachment #8614035 -
        Attachment is obsolete: true

        Attachment #8614036 -
        Attachment is obsolete: true

        Attachment #8614035 -
        Flags: ui-review?(philipp)

        Attachment #8614036 -
        Flags: ui-review?(philipp)

        Attachment #8614044 -
        Flags: ui-review?(philipp)

    
  
User Story: (updated)

    
    

    
  
Comment on attachment 8614044 [details]
https only.png

That seems pretty straightforward :)
Glad that we didn't need to use a notification here!
I assume that users could still connect to the HTTP version (in the rare cases where they might need to) by just removing the »s« from »https://« in the URL, right?

        Attachment #8614044 -
        Flags: ui-review?(philipp) → ui-review+

    
    

    
  
Oh, and on other question: I assume that we would always show the »https://« part of the URL in green from now on (not just when the user gets redirected)?
Flags: needinfo?(agrigas)

    
    

    
  
(In reply to Philipp Sackl [:phlsa] please use needinfo from comment #8)
> Oh, and on other question: I assume that we would always show the »https://«
> part of the URL in green from now on (not just when the user gets
> redirected)?

yes that is the latest visual style for it.(In reply to Philipp Sackl [:phlsa] please use needinfo from comment #7)
> Comment on attachment 8614044 [details]
> https only.png
> 
> That seems pretty straightforward :)
> Glad that we didn't need to use a notification here!
> I assume that users could still connect to the HTTP version (in the rare
> cases where they might need to) by just removing the »s« from »https://« in
> the URL, right?
Flags: needinfo?(agrigas)

    
    

    
  
(In reply to Philipp Sackl [:phlsa] please use needinfo from comment #7)
> Comment on attachment 8614044 [details]
> https only.png
> 
> That seems pretty straightforward :)
> Glad that we didn't need to use a notification here!
> I assume that users could still connect to the HTTP version (in the rare
> cases where they might need to) by just removing the »s« from »https://« in
> the URL, right?

Yes.

    
  
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Rank: 5

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: