Jump to content
  • Announcements

    • boen_robot

      Guidelines and Netiquette   03/28/2017

      Posting Problems:   Having problems posting your topic? Read through this: To join, you agree to our terms and conditions and fill out and submit a registration form. An activation email will be sent to your email adress, so you'll need to verify your account. After that the account has to be validated by one of the moderators. This will mean that it can take up to a day to be activated. A couple of things to remember to ensure approval: Don't use an email address in one of those $2 four character .com domains eg. xyds.com. These will be deleted and the domain added to the banned list. Don't use an email address that is within a domain with a bad reputation for spam. A Google search is run on every email address and email domain. Don't sign up with an email address that doesn't exist, doesn't work or requires the sender to answer a quiz before their email can get to you. Put your country and or state and city in the signup form. Blank forms will go to the botton of the "to do" list. And make sure that your email address and your country match, saying you're from Alabama and using a .ru email address is not going to get you activated. After a membership is activated the first few posts will be monitored. Posting spam or unapproved topics described in the agreement results in an immediate ban. The email provider and the IP addresses associated with the account will be banned and all posts will be deleted. These strict measures have been deemed necessary to hinder spam. Sorry for any inconvenience this causes, but it's not liable to change. If, after reading this, you still can't post and don't understand why, contact one of the Moderators listed here.   Topic Guidelines   Including the following information can expedite an accurate response from board members: Must be a Specific Problem or Question related to web design and development Include Code in Question (wrap with   for small blocks of code and for longer blocks   ) Include Code Author Include Extra Notes/Modifications/Attempts Include web link to page/file when possible Content Guidelines   You may not post, upload, link to, or email any Content that contains, promotes, gives instruction about, or provides prohibited Content. Prohibited Content includes any Content that breaks any local, state, county, national or international law. Prohibited Content also includes: No direct or indirect advertising or websites, forums, products, services No hijacking of posts (do not post your question in someone elses) Content that infringes upon any rights [ex. MP3s and ROMs] (including, but not limited to, copyrights and trademarks) Abusive, threatening, defamatory, racist, or obscene Viruses or any other harmful computer software False Information or libel Spam, chain letters, or Pyramid schemes Gambling or Illicit drugs Terrorism Hacking or cheating for internet/online games Warez, Roms, CD-Keys, Cracks, Passwords, or Serial Numbers Pornography, nudity, or sexual material of any kind Excessive profanity Invasive of privacy or impersonation of any person/entity Hacking materials or information Posting Tips   There are more BBcodes than there are buttons for on the reply menu. To get the full list, click "BB Code Help" underneath the clickable smilie face menu. Use   for small snippets of code Use   for lengthy snippets of code Use   if your snippet is HTML (optional) Use   if your snippet is SQL (optional) Rules of Conduct   Be nice. There's no need for calling someone stupid if they ask an 'easy' question. Keep your avatars and signatures absolutely child friendly. We have a younger audience on this forum. Keep your language appropriate for the same reason above. Do not PM moderators for help on the forum. Post on the topic, or create a new one.   Spam:   Recently, as you have all without doubt noticed, we have had lots of spam and advertisement on the forum. Therefore, we'd like to alert you as to what to do when you have found any of the aforementioned annoying messages: it. Immediately. Give a clear reason, please, if the advertising is not evident. DO NOT POST! Report, let the post stay as is, and we will get to it, meanwhile if you continue to post as normal in the other threads, it won't be on the top so long. Refrain from PMing the member. This won't help at all, as they are most likely spambots anyway. Thank you.       Images in signatures:   After thinking of users on dial-up, we have decided to enforce the following rules regarding signatures. Please pay heed to them. Respecting these rules is respecting the members on this forum with dial-up. Signature rules: No animated images AT ALL. No matter the amount of animation. Maximum image widthxheight: 300x150 Maximum image (file) size: 15kb Use calm colors. Do not use highly contrasting images in your signature, as this can get really annoying when seeing several posts from one member in the same thread. The same prohibited content goes for images as for posts. Lastly, use common sense. No lengthy signatures please. Save us some scrolling. Thank you.       Links in signatures:   Please understand that w3schools.com only exists because of voluntary work and is barely supported by the advertising littered throughout the tutorials and the forum. So, please, stop advertising other sites. DO not post links that drive traffic away from the w3schools domain - especially to a site that offers similar if not identical information. Please help support the site by keeping individuals on it. Thank you. Here are some guidelines as to what you can put in your signature: w3schools links --> allowed w3.org links --> allowed browser links --> allowed html editor links --> allowed personal sites --> allowed tutorial sites competing with w3schools --> NOT allowed sites completely irrelevant to webprogramming and this forum --> NOT allowed   Thanks for understanding, and for taking the time to read this. ~W3Schools Modstaff~
iwato

Same Page, Three Experiments, Two Different Results

Recommended Posts

EXPERIMENT ONE: Open to the Grammar Captive Podcast Hostpage without a Query.

Observe the vertical alignment of the sidebar in relationship to the page's banner.
If you experience the same as I, the sidebar will be top aligned with both the navigation and middle content panels.

EXPERIMENT TWO: Open to the Grammar Captive Podcast Hostpage with a Query String Attached to the HTTPRequest

  1. Open to the Proxy Request Page.
  2. Click where it says Proxy Link.
  3. Observe the middle panel that opens.  It should be a reference to Podcast No. 21.

Observe the vertical alignment of the sidebar in relationship to the page's banner and other aforementioned elements. 
If you experience the same as I, the sidebar is no longer top-aligned with the page's navigation bar and middle content panel.

EXPERIMENT THREE: Repeat Experiment One, but Open to the Podcast No. 21 Panel from the Already Opened Page.

  1. Click where it says ALL in the navigation bar.
  2. Click on the phrase Podcast Index ...
  3. Find Podcast No. 21
  4. Click where it says Discover more ...
  5. Click on the command Click and Listen.

Observe the alignment of the sidebar.  It remains top aligned with the navigation bar and middle panel.

QUESTION ONE:  How might one explain this phenomenon?

QUESTION TWO:  And, what corrective action can be taken to prevent it?

Roddy

 

Edited by iwato

Share this post


Link to post
Share on other sites

For some reason with Experiment Two, the pagewrap element is not enclosing the sidebar and footer elements, the border along with bottom margin appears wrapping round the header only, which pushes the unenclosed sidebar down.

I think you have a extra misplaced closing div after closing main tag, as when viewing page source, the last div is highlighted in red, indicating there is no relative opening div tag to go with it.

  • Thanks 1

Share this post


Link to post
Share on other sites

I will check.  I use BBEdit as my software and regularly use its HTML checker to insure proper that my HTML elements are properly specified.  I have noticed that the editor does not know how to account for the presence of PHP and confuses the opening and closing tags for PHP with HTML.  I will suppress those tags and check again.  Let's see what happens.

Thanks.

Roddy

Share this post


Link to post
Share on other sites

I just checked with the suppression of the PHP element, and my editor could find no error.  

Any other suggestions?

Roddy

Share this post


Link to post
Share on other sites

OK.  I did a very thorough check of the HTML page podcast.hostpage.php and even revised certain aspects of the HTML and javascript.  What I found were several structural problems that were not picked up by the BBEdit HTML checker including a <header> element that had not been closed, as well as unclosed <li> and <p> tags.   I learned an important lesson.  All that appears well, may not be well.  Correcting these errors, however, did not solve the problem.

Please try again.

Roddy 

Share this post


Link to post
Share on other sites

I checked again and the problem still exits? Are there any php/JavaScript code that is generating an extra unnecessary closing div.

A browser will attempt to close elements with no closing tags, but it doesn't always get the placement correct.

Share this post


Link to post
Share on other sites

I do not see any.  There are quite a few HTML comment tags,  and I am generally suspicious about how they function in the presence of other code.  Do you see a potential source of problem in the use of HTML comment tags:  

<!-- ... -->

Roddy

Share this post


Link to post
Share on other sites

Well my editor Netbeans highlights jquery code with html comments within them as missing a end quote, so i removed these html comments and warnings disappear? but it could be over sensitive, which it can be, very annoyingly sensitive.

Your html code now shows me through editor, that you have misplaced closing div just before closing main element.

Share this post


Link to post
Share on other sites

Ex 2;

https://validator.w3.org/nu/?showsource=yes&doc=http%3A%2F%2Fwww.grammarcaptive.com%2Fpodcast_hostpage.php%3Fhash%3D30a6836a3f7c5fc57751a61098e5c221%26podcast_no%3D21#l452c96

Compared to

Ex 1

https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.grammarcaptive.com%2Fpodcast_hostpage.php&showsource=yes

Ex 3

https://validator.w3.org/nu/?showsource=yes&doc=https%3A%2F%2Fwww.grammarcaptive.com%2Fpodcast_hostpage.php%3Fhash%3D30a6836a3f7c5fc57751a61098e5c221%26podcast%3D21

Even though they have errors, they don't have misplaced or extra closing elements, which is causing alignment issue because the wrapper only wraps the header and does not wrap sidebar OR footer elements. The wrappers bottom margin causes the misalignment of sidebar.

Edited by dsonesuk
  • Thanks 1

Share this post


Link to post
Share on other sites

Thank you, Dsonesuk!

The gap was removed when I eliminated the bottom margin.

Solving one problem appears, however, to have created another.  Please compare the placement of the footer in Experiments One and Two!

I had a look at the https://validator.w3.org/nu/ results, and they are certainly more revealing than what I have been able to obtain with BBEdit.  This said, it may be due to my lack of knowledge of the refinements of BBEdit, than BBEdits' short-comings.  I keep discovering more about BBEdit as time passes.

In any case, I must disappear for a couple of hours before I can give them the attention that they are obviously due.

In the meantime, if you have any more suggestions, please let me know.  It appears obvious that the source of the problem lies in the absence and presence of the following two optionally inserted resources:      

 $("<link/>", {
   rel: "stylesheet",
   type: "text/css",
   href: "./_utilities/css/podcast_list.css"
}).appendTo("head");
$("<link/>", {
   rel: "stylesheet",
   type: "text/css",
   href: "./_utilities/css/podcast_select.css"
}).appendTo("head");

 For,  these are absent when the podcast_hostpage.php is accessed with a  query statement external to the webpage (Experiment Two).

Roddy     

Share this post


Link to post
Share on other sites

Hooray!  Hooray!  Hooray! 

Thank you, Dsonesuk.  I found the extra </div> tag and removed it.  Experiment Two now produces an outcome similar to Experiments One and Three.

Two thirds of a day were spent in an effort to overcome this problem.  As always, the time was not completely wasted, for I successfully eliminated the scoped style attribute from my imported <div> and made my page more browser robust.  What is more I was introduced to a new HTML and CSS checker.  But, still ... 

Roddy

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×