You do. When you press submit it sends a http post message with your information. They are not reading your keyboard input on a website. You can verify this with wireshark and any website with a form.
Yeah some places with apps MAY do as you say like Facebook such with full permissions to your phone. That said its still sent as a http post request, just recorded locally and then sent as a giant packet.
That’s why they have the submit button. Otherwise they would have way too many transactions. “a” then “d” then “a” and then “m” and have to concatinate them on the server plus initial packet saying they are getting a first name. Then another that you stopped focusing on first name.
Now how do you handle if I typed adan and go back to correct it? Some apps might do this but general web development(99.999%) doesn’t.
Some apps might do this but general web development(99.999%) doesn’t
Dude, do I have a story for you. A FullStory. I’ve tried to get this removed from my workplaces. But managers take too much time seeing exactly what people are doing on the site in order to determine engagement. So, yeah. Expect every single interaction to be recorded on many corporate websites.
Company computers are different, I definitely don’t trust them. That said managers like that are not good managers. Measure outcomes, not time. When a problem occurs and I can’t figure a solution I go for a walk. 5 maybe 10 minutes. You would be amazed how often I think of the solution on said walk. Yeah it might look like a waste of time but clearing my head is a huge value to the company.
invertedspear@lemmy.zip 1 day ago
You’re right, you can see this with wire shark, or you can just use the network tab in your browsers developer tools.
But as a web developer, you’re absolutely wrong that we can’t collect every freaking keystroke if we want to.
Sometimes we wait for submit. Sometimes we collect everything as you move from one field to another, called a blur event. Sometimes we wait for the user to stop typing for like 1/4 or 1/3 of a second, called a debounce event. But we can collect every keystroke. We don’t concatenate them on the server side, we send the whole field value after each change, tied together with other fields based on a session ID.
Hell, sometimes we track your mouse movements as well. Where you move in the page, where your mouse lingers, how long you hesitate before clicking. A “good” company uses this information to make a better user experience. A nefarious one uses it to collect all your personal information without you ever clicking submit, and sees just how hesitant you were to disengage after being asked to pay. Then aggregate that experience to determine the price point.