Orkut scrapbook broken in Opera and Safari

Tuesday, 20. November 2007, 05:43:25

Many people may have noticed that Orkut recently broke in Opera. As it happens it also breaks in WebKit browsers such as Safari. The reason is that there is a missing closing iframe element. Firefox for some reason reads the closing tag from inside a comment. The Orkut issue is well known, so please don't send any more duplicate bug reports . I've been in contact with Google and gave them the solution (add the closing iframe), and they are looking for someone to fix the issue. It should be fixed for Opera and Safari shortly.

Hated buzz wordsNext generation browsers entering the arena

Comments

"they are looking for someone to fix the issue"

WHAT?

I imagine how your email has reached one employee at google:

"Oh, someone wants to bribe me with tickets to go to an Opera and on a Safari. Oh. Opera and Safari BROWSERS. Ok. Hm. 'need to close a tag'. Tagging, that's this Web 2.0 stuff that Greg is working on I think. But for all I know, he's downstairs playing ping-pong because it helps with his creativity. Maybe Joe can help. He really knows his stuff, last week he helped me figure out how to write ITALICS, that was awesome, he's really good at explaining and found the solution real quick. But I don't see him either. Oh well. I'll just have to look for someone else then. Or... maybe I'll just ignore this email."

By WildEnte, # 20. November 2007, 13:01:51

The contact isn't in the Orkut team, which is why they have to find someone there

By dstorey, # 20. November 2007, 14:26:04

WildEnte, funny

By danigoldman, # 20. November 2007, 16:01:52

Anonymous writes:

in reality, that 'funny' stuff is reality. I do 'work' that way, spending 15 minutes a day sitting at my desk, and whole 8 hours doing 'meetings', 'creative meetings', 'planning' etc stuff.

at first I found it nice, the pace is so slow, after few months it depresses me more than unpaid overtime :/

dont hold your breath waiting for that fix, most probably it was planned for mid feb 2008. until partner or big TV station mentions it, nobody could be bothered

By anonymous user, # 21. November 2007, 07:21:42

So Google doesn't know how to close an iframe? Old news I'd say. The real question is: will IE (or Fx) work after that? Who knows?... standard coding seems evil.

By arthur.titeica, # 25. November 2007, 09:09:41

Yuh. Google has always been depressingly bad at HTML. I'll never understand why a company earning so many billions can't hire frontend guys as well as programmers (or perhaps they do, but don't let the frontend people actually change anything).

"Do no evil" should include "do no evil, and that includes evil by omission"

A bit of support for web standards and accessibility would really help the industry - after all, if Google does something people decide it's good.

By cheshrkat, # 30. November 2007, 13:53:44

niyo writes:

i m hacker

By anonymous user, # 2. January 2008, 16:52:06