Changes between Initial Version and Version 1 of Ticket #24202


Ignore:
Timestamp:
Jan 22, 2015, 8:29:09 AM (9 years ago)
Author:
Håkan W
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24202

    • Property Component UncategorizedForms
    • Property Type UncategorizedNew feature
  • Ticket #24202 – Description

    initial v1  
    11If you're implementing Stripe, Adyen, or other big payment solutions today, then you can use client side encryption, where form fields are used for inputting e.g. credit card number (etc), but that will be encrypted before the form is submitted to the server. These fields should not be sent raw to the server, so you usually remove the name attribute on the input fields.
    22
    3 It would be really useful if django had a SensitiveTextInput widget that just removed its name attribute. This idea is from here: http://stackoverflow.com/questions/18116917/change-form-input-attribute-name-to-data-encrypted-name
     3It would be really great if django had a SensitiveTextInput widget for purposes like this. This idea is from here: http://stackoverflow.com/questions/18116917/change-form-input-attribute-name-to-data-encrypted-name
    44
    5 Suggested class:
     5Here's a suggested class:
    66
    7 {{{python
     7{{{
     8#!python
    89# a text input widget with no name attribute
    910class SensitiveTextInput(forms.TextInput):
Back to Top