Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
psychometry said:
I did, in fact, mean using JavaScript on page load to disable the user from changing the size of the textarea, not within my browser. It's like using CSS to disable the dotted border Firefox puts around links when they are active.

Form elements, and the divs that contain them, often need either fixed widths or have widths that are proportional to their containers.

Take Google. Depending on how the layout is set up (this is just hypothetical), resizing the search box would push those three links next to it off into oblivion if they were all in a div that was fixed or proportional to the page width. It doesn't matter if Safari "dynamically redraws the page" since the div would still be calculated to be the same. Worse yet, depending on its overflow attribute, they could be pushed onto a new line.

I'd really not like to see Safari become the next IE 5. It already has its share of JavaScript bugs. This would just mean us designers would have to spend that much more time envisioning what would happen if a user resized every form element on every page and incorporating it into our layouts. This is why I hope there's a way to disable it outright.
Funny, this was the feature from the list I thought would be most useful. In particular, it would be useful when posting to MacRumors-- I'd love to make this little box bigger...

I hear where you're coming from though. Hopefully Apple would honor CSS clues that the field should remain fixed-- for example if you've set up pixel accurate sizing, you probably don't want it resized.

If nothing else, remember that the user is the one that resized it, not the browser. Even if the other elements get shoved around and the layout made ugly, the user will have seen their actions responsible for pushing things around.
 
ErikGrim said:
You can get this already (along with Tab dragging and dropping) in Safari by getting SAFT:

http://www.pimpmysafari.com

Other free plugins might also have it, but Saft is so good I never bothered to check anything else.

SAFT is a rockstar. I can't imagine using Safari without it. Frankly, I'd be happy if Apple integrates even half of what SAFT provides.
 
The resizable text box will be awesome. There is nothing worse than some lame brain web designer that only lets you see one or two lines at a time when you need to see a lot more.

The solution that was shown on the blog site looked simple and elegant. Its about the user. Listen up you snot a$$ designers. :D :p ;)
 
exactly WHY do we need to resize a text area?

i agree 100%. "dynamically redraw the page"? based on WHAT?

psychometry said:
This is my first post. It takes a lot for me to stop being a lurker, but the idea that any user can resize a textarea on a site I design, dynamically redrawing the page, is among the dumbest ideas I've ever heard. This will break valid page layouts in new and unheard of ways. Designers make form elements a size and shape for a reason.

I look forward to finding a way using JavaScript to disable that feature the day that browser is released.
 
narco said:
Sounds awesome, but I'll still stick with Camino until Safari speeds up a bit and is more stable. Those were my only two issues.

Fishes,
narco.

HUH? Camino is slow as ****!
 
NickCharles said:
HUH? Camino is slow as ****!

Are you sure you're using the latest Camino? I'm not sure what things are like on the mactel side but on PPCmacs, Camino is hands-down faster than Safari- an advantage that becomes more obvious the longer you surf without restarting the browser...
 
I don't know about you guys but I have Windows/OS X and for the windows part I am falling in love with Opera it is the fastest browser for windows, in is small with tight coding and it doesn't use all your RAM. I hope this comes to mac if it does well that would be the ****
 
JONNYCHO said:
I don't know about you guys but I have Windows/OS X and for the windows part I am falling in love with Opera it is the fastest browser for windows, in is small with tight coding and it doesn't use all your RAM. I hope this comes to mac if it does well that would be the ****

ummmm...
 
I wouldn't be surprised to see Leopard ship at Macworld, to beat Vista to the stores and undercut them once more. Will Jobs do it?
 
psychometry said:
This is my first post. It takes a lot for me to stop being a lurker, but the idea that any user can resize a textarea on a site I design, dynamically redrawing the page, is among the dumbest ideas I've ever heard. This will break valid page layouts in new and unheard of ways. Designers make form elements a size and shape for a reason.

I look forward to finding a way using JavaScript to disable that feature the day that browser is released.

Wow, you must really freak out about cascading style sheets too. Bit of a control freak?

Look: the page design is for the benefit of the USER, not the designer. If the page looks like crap if a text area is resized larger than you expected, what's going to happen when a new browser comes out that uses a larger default font in the text area, or adds additional margin padding, etc? If that will make it look like crap, then that's your problem, not the user's!

The problem with text entry boxes in (so far as I can tell) every single browser out today, is that they are fixed width. I can have a nice big 30" monitor and want to be able to type a paragraph about this size in a single friggin' line of text across the whole monitor (more common is trying to convey source code in a text window; wrapping really sucks for source code). But, I can't, because the text box is default sized so that it fits without scrolling on my mother in law's 10-year-old 15" CRT set at 640x480. So, it's a little postage-stamp square on my 30" cinema.

The solution to date is that the user, if they're smart enough, opens up TextEdit (or Notepad), edits their text however they want, then cut/paste into the anemically-sized text box on the browser. The ability to skip the middle-app simplifies things tremendously.

One design suggestion (if Apple's listening): also provide some kind of a widget to "snap" the text box back to it's original size.
 
jettredmont said:
The problem with text entry boxes in (so far as I can tell) every single browser out today, is that they are fixed width. I can have a nice big 30" monitor and want to be able to type a paragraph about this size in a single friggin' line of text across the whole monitor (more common is trying to convey source code in a text window; wrapping really sucks for source code). But, I can't, because the text box is default sized so that it fits without scrolling on my mother in law's 10-year-old 15" CRT set at 640x480. So, it's a little postage-stamp square on my 30" cinema.

Unfortunately this is more of an issue with the designers, and not the technology. It's quite easy to make a textarea that resizes with your site design (unless the site is fixed with... but any site that heavily relies on user input generally is not.. and should not be). takes a few width: 100%'s, and you're good to go.

Now of course, that only deals with horizontal scaling. But hey, try making a post here, and click on those up and down arrows in the top right of the input area.
 
ero87 said:
woah mama. Is that video legit?!! what was that iPod-like thing at the end!

nah, pretty sure that last part is doctored - fun though :p
 
Resizable textarea's have been implemented in WebKit nightlies for a few months now but were turned off by default at some point.

For this to be included in a front page news item when its been publicly available for months is ludicrous.
 
pewtermoose said:
Resizable textarea's have been implemented in WebKit nightlies for a few months now but were turned off by default at some point.

For this to be included in a front page news item when its been publicly available for months is ludicrous.

Yeah, there haven't been any Page 2 rumors recently, either. At least half the stuff from the past 2 weeks should be there instead.
 
I quite understand why the web designers are complaining about this - it means that users can screw up something they have spent ages sorting out. But that already happens - enlarge the text size/window size/screen resolution adn everything goes out of whack. You're not telling me that the pages are designed to look marvellous at every combination of the above?! And that, ladies and gentlemen, is why I hate doing web design. Paper doesn't have that problem - users can't fool around with the end product. But that's the way we're going, so you'd better get used to it, or move back into the paper industry...
 
People here seem to really be freaking out about this textarea business. Its really not that big a deal.

How many users are going to resize the textarea so large that its double or quadruple its original size? - Probably not too many and unless you have a layout that tries to deal with every edge case perfectly, your site is going to break a bit.

Now in the real world most users - if they even bother to resize at all - are going to expand it just enough to make it easier to write in, probably not making it even 1.5x original size.

In most cases your layout is not going to break if you've put any thought into it.

Finally, are we all forgetting that WebKit supports min/max-width and height? This DOES apply to textarea's so everyone can stop freaking out about users breaking their layouts. Though I must say, having used the feature it is quite handy so don't knock it until you've tried it - and I am a web designer so I do realize the havoc it can wreak.

No need for user agent sniffing. No need for Javascript hacks. A couple lines of standards compliant CSS is all thats needed.

The Safari/WebKit engineers are some very smart and talented people - that people would assume that they would go off and implement such a feature willy nilly without giving any thought to it like people are implying is an insult and plain rude.
 
jettredmont said:
If the page looks like crap if a text area is resized larger than you expected, what's going to happen when a new browser comes out that uses a larger default font in the text area, or adds additional margin padding, etc? If that will make it look like crap, then that's your problem, not the user's!

That's why we use style tags to set a default font (yes, even in text areas) or fixed margins. If the W3 gives us the tools, then why should the browser render them void? That just makes no sense.


ChrisA said:
We should get back to the way HTML markup is envisioned. The author tags the test by functions like "title" or "larger" and the browser descides how to display it

That's the most ridiculous statement I've read in this thread so far - and there are quite a few.
 
Draggable tabs is really good news. I like the way things are being gradually improved too. I think Leopard could be a pretty polished OS when we see it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.