untitled.bmp | The Coffeehouse

Koogle
I'm a Terminator - Astalavista, Vis7a!

untitled.bmp in ie7 when trying to "save picture as"

so what is the solution that solves this stupid issue that doesn't happen in other browser engines?

Has this been fixed in ie8 yet or will this most retarded issue still be affecting ie8 users?

littleguru
<3 Seattle

delete the temporary files, reload the website (CTRL + F5) and try again...

It's a stupid issue and I hope they fix it.

Koogle
I'm a Terminator - Astalavista, Vis7a!

"delete the temporary files, reload the website (CTRL + F5) and try again"

nah that doesn't work always.. certainly not now anyway and I even opened the browser with no tabs opened, cleared cache.. restarted tried site again and still untitled.. checked addons not many on, and few enabled.

I did noticed that if you check the properties on an image.. if the Size of the image is stated then you are able to save the image in its original format, with proper filename most the time.. but if the properties says "Size: Not Available"

then your screwed and the best effort IE7 can do is give you untitled.bmp which is pathetic! I mean it can't even get the original filename... I mean then I would be one step away from just batch converting saved .bmp files into some more reasonable format.

And this issue has been in IE6...long wait.. IE7.. still waiting IE8...

Sort it Out IE Team! = so damn imcompentent.

TommyCarlier
I want my scalps!

Calling the developers incompetent (not imcompentent) is a bit easy, isn't it? Have you ever created a browser with the complexity, legacy and backward-compatibility as IE? You have no right to judge people you don't know like that.

ZippyV
Fired Up

TommyCarlier wrote:
Calling the developers incompetent is a bit easy, isn't it?

It sure is if you look at the competition.

TommyCarlier
I want my scalps!

Comparing with the competition is a bit easy, isn't it? Wink

littleguru
<3 Seattle

TommyCarlier wrote:
Comparing with the competition is a bit easy, isn't it?

Tommy has a point here. It's easy to call somebody something without being able to create a better solutions...

Still it would be awesome if flaws like these are fixed in the final version of IE8 Smiley

Minh
WOOH! WOOH!

At least he didn't say "developer incontinence"

Haha! Yes, I laugh at my own jokes!

CannotResolveSymbol
{insert caption here}

TommyCarlier wrote:
Calling the developers incompetent (not imcompentent) is a bit easy, isn't it? Have you ever created a browser with the complexity, legacy and backward-compatibility as IE? You have no right to judge people you don't know like that.

Methinks it's time for a rewrite-- their existing code probably sucks from a maintainability perspective, and it definitely sucks from a user's point of view (slow, bloated, non-standards compliant).

If the decision were up to me, I'd leave IE around for legacy support (so that we don't go around breaking people's apps) and start working on a completely new codebase (maybe even using Webkit or Gecko as a backend-- not that Gecko at this point is probably a good choice from a maintainability perspective either).

Koogle
I'm a Terminator - Astalavista, Vis7a!

look Tommy I don't what your game is defending the IE team you obviously feel they have done such a great job that you feel personaly resposible for sticking up for them? Can't they defend themselves and decisions?

"complexity, legacy and backward-compatibility as IE"

and everyone one of those points are poor crutch excuses as to the reason why IE suks. Its just bad decisions one after the other perhaps IE is aimed at the most primitive of web users who won't notice such issues until mass influence has persuaded them to use other products and they see better features done better elsewhere.

"You have no right to judge people you don't know like that."

yeah whatever deal with it. I think president Bush is a conniving little sh\\t.. is ok to judge someone so long as its of a good opinion?

Now I wouldn't be calling the whole IE team imcompetent for no reason but there are PLENTY of reasons for that call. Quite franky I don't see how a whole team can let certain issues slide past like that. Now I don't have any issues with the guys on the team I'm sure there are some talented people working there.. but whoever is making the design decisions on IE there needs a wake up call!

TommyCarlier
I want my scalps!

I'm not defending the IE team, I prefer Opera and only use IE if it's really necessary. I was just making a general remark that you can't just call people incompetent without knowing the people or the reasons behind certain decisions.

SlackmasterK
I write my OWN blogging engines

Minh wrote:
At least he didn't say "developer incontinence"

Haha! Yes, I laugh at my own jokes!

Inconceivable!

... You use that word wrong alot. Are you sure you know what it means?

evildictaitor
if( !succeed( try() ) ) { while(true) try(); }

TommyCarlier wrote:
I'm not defending the IE team, I prefer Opera and only use IE if it's really necessary. I was just making a general remark that you can't just call people incompetent without knowing the people or the reasons behind certain decisions.

I don't see why not. One of the reasons browsers are so hard to write is because of the way HTML is implemented. If HTML were well defined in the bad cases (specifically rejecting bad pages) then browsers would be much easier to write, would be more backwards compatable and more interchangable and would have less funny breaking changes between firefox and IE.

Now one could argue that those poor old folk on the IE team are having a hard time because they have to work with such a horrendous backwards incompatable mess that is HTML, but if they stopped and thought about it for a second, they'd realize that a number of the problems with HTML stem from the fact that they screwed up (and screwed others) while implementing earlier versions of HTML.

Microsoft should expect its market share in the browser market to steadilly decrease to around the 40-30% mark. If they really wanted to stay on the top of the market they should implement a better system with the following:

1. Bad pages are rejected - thus avoiding the need to have consistent failure processing between versions.
2. A well defined data encapsulation language - if you're going to have styles, don't have <b> and <i>. If you don't intend to have a feature in future, don't include it (<marquee> and <blink>).
3. Write down a good, clear and concise definition of the language and how they are drawn and rendered.
4. Make it so that while the data can be extracted, the layout and non-content images can't be trivially extracted. The internet's casual approach to stealing javascript and other code means that the value of online IP development is much less, and means that little R&D goes into online web-experience development, compared to say, gaming.
5. Write the program in C++ and use RAII (or hell - if you're starting from scratch use C#). This way you won't have the memory leaks, buffer overflows and ridiculous security problems that meant that people went away from IE in the first place.

littleguru
<3 Seattle

CannotResolveSymbol wrote:
Methinks it's time for a rewrite-- their existing code probably sucks from a maintainability perspective, and it definitely sucks from a user's point of view (slow, bloated, non-standards compliant).

What do you think do they do with IE8 and the new engine... check out the videos here on Channel 9 about the next IE version to get the details Wink