[Mermoz]

First of all, excluse my complete ignorance. I am not even sure if this is HTML. In any case, this is my problem: in a certain mail server, you can choose as many aliases as you want, and they do appear as the sender's name in the messages as they are reveived BUT always accompanied (in parentheses and immediately after the alias) with the real email (which, of course, I don't want to show, at least not in a first, quick reading of the message).

When I try to delete the real email so that the emails sent show only the alias , I can't (the real mail box appears in gray and cannot be erased nor overwritten). Going through the scripts, I have found this:

<td>
<input id ="rcmfd_mail" class="disabled
ff_mail" type="text"
value="realemail.at.something.dot.com"
name="_email" disabled="disabled"
size="40"></input>
</td>

My question is: can I add some script in order to reverse this disabled form and thus procede to delete the "real email"? And, if so, what script and where exactly do I have to write it?

Very grateful in advance,
Mermoz

[SIM-2015410]

Try deleting the word "disabled" from the class attribute, and the disabled="disabled" attribute. Then you should be able to edit it

[Mermoz]

Thanks for the reply.

I have done what you suggest, but as soon as I exit the java (?) script and go back to the "normal" page, the real mail reestablishes immediately itself in the box where it was previously shown, and when I come back to the script the old "disabled" orders I deleted reappear. Whatever changes I introduce are reverted when I go back to the main page, as by default.

Any hint?

M.

[JIM NASIUM'S GYMNASIUM]

Thanks for the reply.

I have done what you suggest, but as soon as I exit the java (?) script and go back to the "normal" page, the real mail reestablishes immediately itself in the box where it was previously shown, and when I come back to the script the old "disabled" orders I deleted reappear. Whatever changes I introduce are reverted when I go back to the main page, as by default.

Any hint?

M.

Well, yeah. What did you expect to happen? It would be pretty retarded if anyone could open the developer tools and make permanent changes to a website that would effect anyone that uses it.

When you use the developer tools to modify the DOM of a particular website you're on, you're only editing a local copy of the HTTP response that your browser received from the server. Every time you send a GET request to a web server, it responds with a whole bunch of HTML, CSS, and JavaScript, and your browser interprets that to display a functional web page to you. You are free to edit the content of this page as it only really exists inside of your browser. As soon as you refresh the page, the process starts all over again, and your browser now has a fresh copy of that HTTP response instead of the content that you edited earlier.

The only way that you're going to be able to automatically keep the 'disabled' attribute away from that particular element would be to write a Chrome extension that removes it when the DOM has finished loading. Otherwise, you're going to have to manually make that change every single time.

[Mermoz]

Mrparkers,

Thank you very much for this truly informative answer. As I said, my ignorance is almost absolute; now at least I understand what is going on.

Could you elaborate oin de Chrome extension needed, or at least point to me to where I can learn to do it?

Grateful in advance,
Mermoz

[JIM NASIUM'S GYMNASIUM]

I've never written a Chrome extension before so I might not be the best person to ask. From what I understand, Chrome extensions really just load some Javascript on each page once the DOM is ready. So you'd have to write some Javascript that checks for the disabled attribute you want to remove, then remove it.

[SavageBoys]

You don't need to make a chrome extension, extensions exist already for forcing your own CSS and even Scripts on a page.

Grab Stylish, create a new style for the page, override the .disabled {} class in the css with your own code to stop it from styling the element.

Though seeing as it is disabled inline (disabled="disabled") which effects the form itself.. you need a way to edit the HTML as well as the CSS I believe so an extension like greasemonkey may come in handy.

If its greyed out that is probably what the .disabled class does so other than overriding any opacity or color adjustments you may not need to do much there.

[JIM NASIUM'S GYMNASIUM]

You don't need to make a chrome extension, extensions exist already for forcing your own CSS and even Scripts on a page.

Grab Stylish, create a new style for the page, override the .disabled {} class in the css with your own code to stop it from styling the element.

We aren't talking about a custom class named 'disabled', we're talking about the HTML5 disabled attribute. Modifying CSS will not help here, it will require some Javascript.

[SavageBoys]

We aren't talking about a custom class named 'disabled', we're talking about the HTML5 disabled attribute. Modifying CSS will not help here, it will require some Javascript.

Yeah I mentioned that.

You cut off half my post.

[JIM NASIUM'S GYMNASIUM]

The second half of your post mentioned editing the CSS, which does nothing to affect the HTML5 disabled attribute, as well as modifying the .disabled class, which also will have no affect. I decided to leave it out because it seemed clear at that point that you thought we were talking about a class and not an HTML attribute.

[SavageBoys]

The second half of your post mentioned editing the CSS, which does nothing to affect the HTML5 disabled attribute, as well as modifying the .disabled class, which also will have no affect. I decided to leave it out because it seemed clear at that point that you thought we were talking about a class and not an HTML attribute.

Spoiler (Click to View)

I know. That is why I suggested GreaseMonkey.