Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

technical issues with XHTML / HTML 3

Status
Not open for further replies.

090485

Programmer
May 23, 2008
11
GB
Hi All,

First of all i just want to say thank to everyone who can help me and probably other as well with this thread.

I have searched the web and i cant come across to any site wher it explains some techincal issues with XHTML or HTML, I mean what kind of techincal issues could arise in XHTML or HTML. I'm trying to prepare for an interview and they are gonna ask me various technical questions. Would any programmer or a Techincal user or anyone, might have an idea of a techincal issues, please write them in this thread and help me out........

I hope to hear from you guys......

Many Thanx
 
What kind of technical issues are you talking about? The only thing I can think of is that some elements or attributes that exists (and are valid) in HTML do not exist (or are deprecated) in XHTML. While most browsers would still render the element correctly, there's no incentive for them to do so. Future browsers might not have this backwards compatibility anymore and simply ignore the elements/attributes that are invalid.

___________________________________________________________
[small]Do something about world cancer today: Comprehensive cancer control information at PACT[/small]
 
Hi again, sorry i should have made my self more clearer.

for example i mean a question might come up in an interview saying "what should the developer include in an HTML page to avoid going into quirks mode?", more techincal questions that can be raised or perhaps some possible interview questions?

Hope this helps a bit more.........
 
what should the developer include in an HTML page to avoid going into quirks mode?"

A complete, and proper DOCTYPE.

Additionally, including an XML declaration at the top of a document can throw some browsers off. Although it technically should be there, you can safely leave it out unless your server is set up to serve XHTML as XML data.

--
Tek-Tips Forums is Member Supported. Click Here to donate

<honk>*:O)</honk>

Tyres: Mine's a pint of the black stuff.
Mike: You can't drink a pint of Bovril.


 
an other question.........

just a bit out of the thread though....

i have built a website ( ), it is on one page and consists of div tags that are controlled through JavaScript....
i have been asked
"what if the user has disabled javascript on their browser? how can i make sure that my website still works?" Can anyone help me with this please.....

is there a way around it or not.....?

Thanx
 
The link to your site doesn't work, however what do you mean "div tags that are controlled through JavaScript"? What "controlling" are they doing? Why do you need javascript to accomplish whatever it is you are doing?


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]
 
An interviewer is likely to try to test how comprehensive your knowledge of (X)HTML is. So, I think swotting up on what you call the "technical issues" isn't adequate. What you need to do is immerse yourself in all things (X)HTML (e.g. standards, reference sites, tutorials, books and real-life examples - i.e. visit websites and view their source).

It's like an exam - you know the subject area being tested, but not the specific questions, so you try to gather as much knowledge of the subject area as possible.

Clive
Runner_1Revised.gif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer." (Paul Ehrlich)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
Sorry the site is .co.uk NOT .com, my bad.........


Basically i am supposed to have 5 pages in total but i only have 1 page and have various div tags and the content for each of those pages are in those div tags, so when teh user click's on a page link a new page does not open, however a div tag opens and that is with the help of javascript.........
 
I just tried disabling Javascript, and the effect is that I cannot view any of your page content except your home page. So disabling Javascript, effectively cripples your site, as you are unable to navigate it. I would advise against using Javascript to provide access to each of your "pages". Javascript should be used to enhance the behaviour of your site, without detrimentally affecting those who don't have Javascript enabled.

Theoretically, if you did use this "controlling" behaviour of Javascript, you should ensure that all the content is visible by default.

Clive
Runner_1Revised.gif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer." (Paul Ehrlich)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
would that mean i have to build each page on their own?
also, if i have all the content visible by default that means they will all be on top of each other unless i have separate pages........? am i right or wrong?
 
Any reason you feel you have to re-invent frames, and then make them inaccessible to non-JS users? While it works with JS enabled, and with minimal page content, it will be slow loading and ungainly when it starts to grow.

Why not do it the normal way, using Includes for your fixed content?

___________________________________________________________
If you want the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller
Steam Engine Prints
 
I'm not advising this route (I, personally would go with what johnwm suggests, using server-side includes for unchanging content - header, navigation and footer), but to ensure content was visible by default, you would need to remove the absolute positioning on #tab2, #tab3, #tab4 and #tab5 and remove the height constraint of 656px that you place on #main_body (scrollbars apart from those belonging to the browser window, are not a great idea anyway, in my opinion). This would allow the tab divs to appear sequentially down the page. You could then use the Javascript to hide all tab divs except the one you wish to show.

Clive
Runner_1Revised.gif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"To err is human, but to really foul things up you need a computer." (Paul Ehrlich)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To get the best answers from this forum see: faq102-5096
 
Hmmm.

When is your interview?

How can I put this nicely without being unintentionally offensive? :)

I don't know what role you are to be interviewed for but if it's a web design/development position I would say that you really need to do some swotting.

what if the user has disabled javascript on their browser? how can i make sure that my website still works?

Who asked this?

None of us know everything and everyone has to learn somewhere but instead of asking specifics as you have done I really do think you would benefit from getting a broader understanding of the subject.

It goes without saying really that if you use Javascript to show/hide content on your page then you need to be aware that users without Javascript will not be able access that content.

The way you've built that site is insane. There is no real logic behind your method. Why did you do it that way?

It CAN be done in that manner but I can't see the benefit. The trick would be to show everything by default then use Javascript when page has loaded to hide everything except the first 'page'.

Then again, why not just do it properly?



It does appear to me that you are lacking some fundamental knowledge of how the web works. This is pretty basic stuff for anyone wishing to become a web professional.

I almost feel that if you are using these answers to get through an interview for anything other than a trainee then :

1. You aren't really going to understand the reasons behind what has been said
2. You are going to be in a job, out of your depth and thus selling your employer short
3. You are going to wind up in the mire at some point pretty early on when you 'drop the ball'

It's all pretty basic, 'web 101' sort of stuff.


Now, I know I've been pretty rough on you there and I hope you are big enough to understand I'm trying to help.

When is your interview, and what is the position you are applying for?


--
Tek-Tips Forums is Member Supported. Click Here to donate

<honk>*:O)</honk>

Tyres: Mine's a pint of the black stuff.
Mike: You can't drink a pint of Bovril.


 
I think what I'm trying to say is that there is a bigger picture that you need to be aware of and it might take a bit of time to get there.

--
Tek-Tips Forums is Member Supported. Click Here to donate

<honk>*:O)</honk>

Tyres: Mine's a pint of the black stuff.
Mike: You can't drink a pint of Bovril.


 
<b>Foamcow</b>

Thanks for your advise..........i havent got an interview yet, but if i do go for it, it would be front end developer, purely HTML/XHTML/CSS only........
 
Can someone lead me to a website or any resource that will give me the fundamentals of how the web works, such as whats the best way and what the bad way to build a site, basically the fundamentals of how the web really is supposed to be.......?

Thanx
 
If I did not know something i would not go on an interview, why humiliate yourself for no reason?
They will find out if you have no real world experience, they will ask you some stuff you can't find in books or very specific things and then what?

Denis The SQL Menace
--------------------
SQL Server Code,Tips and Tricks, Performance Tuning
SQLBlog.com, Google Interview Questions
 
its not humiliating urself, its just called getting somwhere ln life, if i do happen to go to an interview in all honesty i dont think i will get the job at first or even the second time, its the experience that you get from the interview, and lets be real in here, the only best experience there is in this world is actually working on the project rather than just learning.....i understand what ur trying to say, but i wouldn't call it humiliating, i would just call it, getting prepared for the future....its not like the person knows me and is gonna tell all my friends my interview went bad, no it gets done and dusted there and then, all u gain is the experience........beside i never said im going to an interview, its too early in a stage for me to do that, i was just gathering information........
 
im asking for your help guys......if you know a site that will explain the fundamentals of how the web works please forward them to this thread, i would greatly appreciate the cooperation.......

Thanks
 
Basically I would suggest you do lots of reading to start off try
Second hang around here a bit. look at other topics. Try to solve problmes posted by other's even if they are already answered. Think of what you would have done in their place, and what was suggested by us.

Look at the FAQ's.

If you browser the web and you find a page that has something interesting look at their source code, chances are you'll find how they got the site to do what it does from the source code.



----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top