I tried to disable Google Chrome's text area resize function by putting this in my text area's CSS "resize: none;" It didn't work. And how do you make a window open in a new page in xhtml strict ('can't use target') Please help!
Google's text-area resize does NOT rely upon the CSS3 state - it's a user interface element I don't think they want developers to be able to turn off in the first place. Welcome to the hell that is the HTML specification so far as forms are concerned - since there is little if anything in the spec that says what the default appearance, behavior or functionality of form elements are. You might be SOL on that. As to opening in a new window, the question would be WHY. It's deprecated from strict because we aren't supposed to be doing that anymore - if the user wants it in a new window or tab they can middle click or ctrl-click, etc, etc... - you shouldn't be shoving that behavior down the user's throat giving them no choice.
Well, then how do you create input textareas without the user being able to screw the look of the whole form by resizing everything! It is for a link to my Terms of Service agreement at the end of my form. I don't want users to finish filling out my form, click the Terms of Service agreement to read it (although most people don't do that anyway) and lose all of their input. (they'd probably leave the entire site if that happened to them) Thanks.
Also, could you tell me how to include a flash file in my site. My flash works on Chrome and IE but not in Firefox. Do you know why it wouldn't? And do you know of any errors that Firefox has with javascript function because I have one for a rollOver and it won't work?
Leave the container around it dynamic, and leave the textarea in flow - apart from that, there's not a lot you can do. Think of it the same way as how Safari ****'s up inputs. The specification makes ZERO mention of these capabilities, so it is ENTIRELY at the whim of the user agent (aka browser) That's HTML for you In that case, take a hint from most forum software - put the agreement on a separate page BEFORE the 'real' form that the user has to click-through to get to where they enter their info. Are you using some script to embed it instead of just using OBJECT directly? Are you using EMBED instead of OBJECT? Are you sure the netscape plugin format version of Flash is installed? (Wait, if it's working in Chrome then it should work in FF) Can you post the code you are using to embed that flash? If we can see the code we can probably fix you up right quick. Not offhand, though on a modern browser like FF rollovers should be handled by CSS, not by javascript; Javascript assist should be reserved for IE6/earlier... Unless you REALLY have your heart set on some goofy animation.
Thanks for the reply Here is the code that invokes my flash file. It works in Chrome and IE but not in FireFox. For Firefox it doesn't give an error, it doesn't even try to load the file, it just expands the div like there was something in it. HTML Code: <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0" width="650" height="500"> <param name="movie" value="http://www.foreverplaying.com/Games/BLADE (Ballistic Light Assault Droid Enforcer).swf" /> <param name="quality" value="high" /> </object> Code (markup): Thanks!
Ok, your flash embed problem is actually pretty simple - you have an outdated/outmoded flash method there... the reason it doesn't work in FF? the "movie" parameter is NOT how you are supposed to call what's to be shown inside an OBJECT tag - that's what the DATA attribute is for! Making it worse, the use of spaces in the filename without putting it in double quotes SHOULD be breaking that in damned near EVERY browser. That it works at all anyplace is actually quite suprising. Sad part is you end up having to say the flash file's name TWICE since some versions of IE are retards about the DATA attribute since they didn't actually get the OBJECT property working how the specification says until IE8... Which is why everyone seems to have forgotten OBJECT was supposed to replace IMG, APPLET and the proprietary EMBED so we had one simple tag to handle all non-text data - so do they ride Microsofts case about it when developing HTML5? No, instead let's introduce two new tags for browser makers to lag behind on... Sorry, pet peeve - I hate the very IDEA of VIDEO and AUDIO tags as they are a step BACKWARDS from what STRICT brought us... but so is MOST of HTML5. Try this: <object type="application/x-shockwave-flash" data="http://www.foreverplaying.com/Games/BLADE (Ballistic Light Assault Droid Enforcer).swf" width="650" height="500" > <param name="movie" value="http://www.foreverplaying.com/Games/BLADE (Ballistic Light Assault Droid Enforcer).swf" /> <param name="quality" value="high" /> <!-- alternative content for when flash is no present should go here --> </object> Code (markup): classID and Codebase also can cause more problems than they solve, so you can just leave those out. They don't do a damned thing that's useful in most browsers anyways. You want a fallback link for when the flash fails, put it where I have the comment. ... and this is just PART of why you don't skip the double quotes, use a STRICT doctype, and run it past the validator.