Comments: Float Handling

That's cool to hear. You can fix the positioning on your personal blog if you used floats for the content and links sections (just thought you'd like to know)

- Pok

Posted by Pokute at March 21, 2003 7:17 PM

Since the seed program is gone, I must report the bugs to you directly that I feel may be relevant to you and the rendering engine.

There is a common problem with many browsers (including safari) where menus don't space out correctly. This appears to be similar code in all circumstances. Moz and IE show it correctly.

One example would be a local cinema's website.
http://www.cinemaworld.org (why it's .org, I have no idea)

Another good example would be the new beta theme for LiveJournal users, but you would have to have an account there for this.

I believe it has something to do with how layers are created and positioned. I reported the bug way back with the original seed and public beta releases, but it is still there.

I'll be more than happy to test out any fixes in places such as LJ where an account is needed, although you'd have to contact me at my Apple.com account, rather than just let the next version get to me, as there is no more seed program. :(

Posted by David Hemenway at March 21, 2003 8:38 PM

does anyone know when we'll see the next public beta?
I'm still using b60 and hearing about these fixes makes me itchy ;-)

Posted by Gregory at March 21, 2003 11:01 PM

Yeah, I'm using the same menu software (Milonic DHTML menus, http://www.milonic.co.uk/menu/">http://www.milonic.co.uk/menu/">http://www.milonic.co.uk/menu/) on one of my sites, and it is indeed broken on b60.

Posted by Indrek Siitan at March 21, 2003 11:40 PM

Ah, and since people seem to randomly report bugs in the comments around here, I might just follow the path. A definite way to hang b60 is to go to http://www.chrysler.ee/index_c.php and click any of the models in the "Valige sőiduk:" list.

Posted by Indrek Siitan at March 21, 2003 11:51 PM

FYI with any of the " Hypothetical" beta's thru say hmm 62 thru 67 or so, a feature that works great in v60 has not worked at all in any of the " Hypothetical" betas.
Mambo Site Server Admin
http://www.opensourcecms.com/mambo/administrator/
username "admin" and password "admin". This will give you full adminstrator privileges. And the admin menus should "Build" at the top of the screen, and they do just fine in v60 but not in any other v since.

Posted by BK at March 22, 2003 5:12 AM

Quick suggestion to all bug-hunters, rather than just repot that page X doesn't work, grab some HTML and code a smaller test page, keep subtracting elements until just the broken bit remains. This will allow the coders to find the problem much more quickly.

Posted by Lou at March 22, 2003 6:53 AM

Indrek, hypothetically with b67 www.chrysler.ee does not hang when selecting a vechile.

Posted by Jussi at March 22, 2003 8:48 AM

re crazy menus... www.lacrosseamerica.com

compare it to how it looks in moz or ie...

Posted by Jack Kennedy at March 22, 2003 9:51 AM

"With all of these fixes macromedia.com's pages render correctly. Woo hoo!"

Cool, thanks very much, David... great news! 8)

jd

Posted by John Dowdell at March 22, 2003 10:35 AM

Excite.com still does not render the "same" as with the latest Camino nightlies. With Camino the columns render in proportion to the window, so that you can see the whole page without resizing or scrolling right, with Safari the middle column is way wide, forcing a lot of sideways scrolling.

Posted by Bill Henry at March 22, 2003 1:20 PM

If there was hypothetically a thing called b67 then it is possible that there could be a hypothetical bug in it where the far left tab always is highlighted no matter what tab is selected, at least hypothetically.

Posted by coolmacguy at March 22, 2003 1:42 PM

excite.com is a known regression.

Posted by hyatt at March 22, 2003 3:11 PM

Although I am sorry to Dave for opening up the bug report issue again...if you are to do this, please keep it to his area of work only. That area would be the display and interpretation of the page..aka, the rendering engine. Things like the tab bug should be reported through the bug button. (Dave, feel free to say to the contrary if you wish, but this is what I remember from previous posts of yours).

Posted by Dave SPOOF Hemenway at March 22, 2003 3:16 PM

Safari cannot properly connect to Mallard (http://mallard.ilstu.edu is my school's Mallard page). Mallard is an online class system developed by the University of Illinois -- it has online quizzes, announcements, that kind of stuff.
Currently, Safari fails to authenticate my login. After entering my password, it boots my back to the login name page. Since you need an account on Mallard to really test this, it's a little difficult for Dave to do so. So, I have to use Camino to take quizzes.
Dave, if you'd like more information, feel free to contact me. I could get you code snippets and such, if needed.

Oh, and please make the inline spell-checking preferences stick.

Posted by Damien Sorresso at March 22, 2003 6:45 PM

Safari shows no horizontal scrollbar here . http://rineke.net/records/jpghtmls/50/IMLP-9048-img727.html It's a big jpeg. Although other browsers show a horizontal scrollbar I don't know what's correct. The code is just this.

- 5 lines of html deleted from post -

PS - sorry about not using the bug button exclusively but...

ber

Posted by ber at March 22, 2003 8:04 PM

Safari has a real problem with the rendering of the java element in this page: http://facs.scripps.edu/surf/buoylist.html

The buoy information is inacessible because the box it is displayed in is very narrow. I guess Safari doesn't know how to handle the width elements in the applet codebase tag. Even scrolling all the way to the right doesn't reveal the full content of the area.

Posted by Michael J at March 22, 2003 9:09 PM

Hey Dave, wonderful job with hypothetical build 67. However, I am noticing that when I page requests a new window (and I have the tab bar always open) a blank window opens in front but the page loads in a new tab in the background. Slightly annoying. Happens at CNN.com, nytimes.com, and some others. Keep up the wonderful work and thanks for the best mac browser!

Posted by Anonymous at March 22, 2003 9:48 PM

Well, that's it, no more hypotetical betas :(

http://www.mac-mike.com/

Posted by Partypooper at March 22, 2003 10:21 PM

Its interesting how people have such a hard time keeping secrets. Especially the Mac lovin' types. Why is that?

In any case, I'll speculate about Safari builds and say that Apple is planning a public release every tenth (v70 is next). And at the current rate, it should be here in about two weeks. How's that for a wild guess?

Posted by freddy at March 23, 2003 12:03 AM

v67 Problem - on the left side, the white text is black. Any reason or fix? Or is it my horrific HTML coding? (Which I don't think it is, as it worked on previous safari builds...)

Posted by Jeremy at March 23, 2003 1:26 AM

"Safari cannot properly connect to Mallard (http://mallard.ilstu.edu is my school's Mallard page). Mallard is an online class system developed by the University of Illinois"

Same problem with Oscar, our system at Georgia Tech (https://oscar.gatech.edu/bprod/owa/twbkwbis.P_WWWLogin). When I attempt to login it gives me this message, "This system requires the use of HTTP cookies to verify authorization information. Our system has detected that your browser has disabled HTTP cookies, or does not support them. Please refer to the Help page for more information on how to correctly configure your browser for use with this system." I have cookies set to accept all.

Posted by coolmacguy at March 23, 2003 8:25 AM

A new bug has appeared with v67 (mmm... found in the street) : with flash content. If a flash movie tries to open an url with the "_blank" parameter, it opens a new window but loads the content in the original window.

Posted by Jerome at March 23, 2003 10:55 AM

well since so many people have posted about "hypathetical" problems with beta 67 i might as well as well. if you go to my blog in beta 67 it does not load the CSS. i do not understand this as it has in all the other builds i have used. and i am 99% sure it is not my codeing or lack thereof. other MT blogs look fine. im basicly using a modified version of one of the default styles. but since this is a "hypathetical" beta, i am sure there are problems with it :)

Posted by Ken Edwards at March 23, 2003 11:52 AM

In theory, Safari *still* fails to draw :hover decorations/boarders on non-text links

see
http://24.44.140.94:24680/galleries/

and mouse over the images. There should be a blue border when you hover, nothing when you mouseout.

this renders properly in the gecko variants [Camino, Phoenix, etc]

Posted by CM Harrington at March 23, 2003 2:18 PM

That's too bad the seeding is closed. It seemed like the whole ~thing~ (a la Mozilla) was working quite well for fixing thing. ;(

Posted by Dan at March 23, 2003 2:21 PM

It's the little trivial things that get to me: Please, sometime soon, include Spacers for bookmarks! Hehe, it's a trivial little thing, but for the love of God, please give me spacers! :-)

I love Safari. Best browser ever. Keep up the good work!

Posted by Jared Rice at March 23, 2003 4:53 PM

I'm not sure what exactly is the problem on the International Herald Tribune site, but it seems that the DHTML layers are not clipped at all on Safari. You can see this e.g. on http://www.iht.com/articles/90737.html. The three text columns are created with DHTML, they should be cut off on the top and on the bottom. Clicking to the left- and the right-most column navigates through the text. (Every column contains the whole text and is moved by a vertical offset when navigating through the text. the clipping should hide the bigger part of it).

Posted by Kerl at March 24, 2003 12:37 AM

Hey Dave... Safari's Java implementation doesn't work with Filemaker Pro driven sites... Wasn't aware if you knew this or not. I can provide you with private access to our server that we get a Javascript 972 error with every time we try to access it (b60)...

Has this been fixed in more recent builds? If so I'll shut up now :)

Sorry to hear ADC won't be distributing Safari builds since certain people have been breaking their agreement and dumping it for the world to play with. I personally would like to see Apple having a nightly build type thing to improve it on a faster basis for bug testing, but Apple is Apple and they don't do that. I understand some of the method to the madness...

Thanks for all of your and the Safari teams hard work! The Apple Community counts the days until IE is no longer the default in our operating system.

Posted by Hey Dave... at March 24, 2003 3:51 AM

A little problem, which is stopping me from installing Safari on the Macs in our office:

In IE, if you select the contents of a table and copy them, they are copied as tab-separated data. You can then paste them into Excel, for example, and the data will be nicely fitted into the cells.

In Safari, if you copy data from a table, each value is separated by a line break, with a double line break between rows. If you try to paste this into Excel, all the data is put in the first column.

(Hypothetically, if there was such thing as a b67 release, I guess it wouldn't work in that either).

I'm sure I'm not the only one who'd like to see this sorted out...

Posted by Seb at March 24, 2003 7:24 AM

I personally have been a big fan of the IE feature of tab-delimited copying of tables. But, as a feature I'd like to see it prioritized below things like fixing float handling. Strong modern CSS rendering is such a rarity in this world and the closer Safari gets to that nirvana the happier I become.

Posted by Gavin Kistner at March 24, 2003 9:47 AM

"Hey Dave..." (kptchris):
Let's not confuse the man. If you're talking about JavaScript, don't say "Java implementation". Java and JavaScript are totally different beasts; the difference is like apples and... potatoes (in French: les pommes et les pommes de terre).

BTW, it is possible to use CDML to create a FileMaker site which does not use JavaScript at all; I know because I've done it.

Since there are many different "internal" pages in FM with embedded JS, it would help if you could determine which of those pages/resources is being called so the offending JS code can be isolated.

Posted by Walter Ian Kaye at March 24, 2003 2:58 PM

I could have sworn there was a little bug icon at top right in Safari?

Wouldn't it make more sense for everyone to post their bugs through the submit bug icon rather than making Mr.H trawl through these posts looking for bugs and missing some, the more time he spends doing this the less time he spends fixing problems .. (and having a life etc).

Posted by Fimbo at March 25, 2003 12:33 AM

Now that's weird: If you go to http://www.orionserver.com/ with Safari, you get a page filled with only chinese letters, from the top to the bottom, with no white space at all!

On all other browsers, there appears normal english text.

A very funny bug indeed!

Posted by Kerl at March 25, 2003 4:41 AM

>Now that's weird: If you go to >http://www.orionserver.com/ with Safari, you get >a page filled with only chinese letters

the source of this pages specifies a bad "charset" , so safari cannot know it's UTF8 or UTF16 characters.


Posted by michel at March 25, 2003 8:31 AM

congrats

Posted by self employed health insurance at February 13, 2004 8:40 PM
Post a comment