TextEdit keep changing the extension to TXT

addfone, I'm having this problem as well, did you find a solution?

just out of curiosity, what is your hardware ur running lion on?

it doesn't do this with .css files for me, just .html files. what about you?

ok so it's not a hardware thing. I'm on a black macbook (2006), core 2 duo, 2gb ram.

yeah I have been using Dashcode in the meantime, but I like using TextEdit for quick html edits. it leaves css files alone, but it's freakin irritating when I save or close the window and it automatically changes the file type...that's just wrong, and a serious bug. I have another thread going about it and some people are having a hard time believing that this is happening:

https://discussions.apple.com/thread/3195606?answerId=15684922022#15684922022

I've been using Textedit exclusively for writing my web sites, for several years. This new behavior is indeed frustrating, and I hope they fix it right away. (You can manually change the extension to HTML after quitiing Textedit, but that's obviously not a good way to work.)

Mike James3 wrote:

I've been using Textedit exclusively for writing my web sites, for several years. This new behavior is indeed frustrating, and I hope they fix it right away. (You can manually change the extension to HTML after quitiing Textedit, but that's obviously not a good way to work.)

My guess is that the fix will be slow in coming. Meanwhile I've resorted to using TextWrangler and as a workaround to having to manually change the extensions after editing in TextEdit. I find it's a much better choice. I will still go back to TextEdit if and when they fix it. I did report it as a bug.

With the help of an Apple Tech Support rep, I downloaded their "Data Capture" app, ran it, and returned the file to Apple, including a screen-capture movie of the above-mentioned behavior. Several days later, I heard back from the rep, saying the the Apple engineers had indeed been able to replicate the behaviour. So, they know for sure that the problem exists for some users, and we can expect a fix at some point.

Cool. Hopefully the fix is sooner rather than later...

Mike James3 wrote:

With the help of an Apple Tech Support rep, I downloaded their "Data Capture" app, ran it, and returned the file to Apple, including a screen-capture movie of the above-mentioned behavior. Several days later, I heard back from the rep, saying the the Apple engineers had indeed been able to replicate the behaviour. So, they know for sure that the problem exists for some users, and we can expect a fix at some point.

Good report Mike James3 !

theemaadhatter wrote:

Cool. Hopefully the fix is sooner rather than later...

I just installed OS X v10.7.1 but that didn't fix the problem.

Same here