There is nothing wrong with Absolute Positioning, this is a widely used property and is here to stay for a long time. The way you are using it is unnecessary that is if you don't display your layers above a fixed background image (<img src="">). If you want to move away from Absolute Positioning, use margins.
I am a heavy user of absolute positioning. It is used, in particular, to build what could be referred to as consoles. One could use relative positioning for this, too, but with a good deal more work (or just different adaptive habits). I use relative, too, in a situation where I produce additional input areas on demand. Content is absolute, out block is relative.
These, in turn, as a block can also be positioned absolutely. Less of a problem now, but it was the only way to make a page design consistent across platforms only a few years ago (IE, for example, was was a horror story).
Don't listen too hard to others' opinions on the latest fashion in HTML development. Tables are/were frowned upon. Snobbery! Sure - you can do more with div's, but if you don't need that "more", life with tables is easier to design and easier to modify.
So - you need to meet your design needs - but only make changes that are either essential or that you perceive will come back and bite your backside sometime in the future.
I am new to front end development I have a requirement to create a online registration form which has attachments and more comments i.e text field.
So I want to start my online form with HTML as it is an open source.
Can anyone guide me how to create a form and upon submission by user it must be either saved as pdf in their local drive and send an email to me or else directly upon submission it should sent to my email directly as pdf.I want to use open source/Excel for front end
I need to create a link on one page (my home page) that links directly to a image on another page already containing multiple images. Thought I knew how to do it...by creating an anchor; & my code looks like this:
a href="theOtherPage.html#PHOTO.png">IMAGE SUBJECT
but it doesn't work. Even tried the forward slash after the page id:
a href="theOtherPage.html/#PHOTO.png">IMAGE SUBJECT
I am facing some difficulties in designing of this <a href="http://www.sarcasticca.com/ca-cpt-registration-form-june-2018/">CA CPT / CA Foundation Registration </a>[<a href="http://www.sarcasticca.com/ca-cpt-registration-form-june-2018/" target="_blank" title="New Window">^</a>]. I don't know what is happening what it doesn't showing the main image.
My class assignment is to develop a functional analog clock using HTML, CSS, and JS. I'm having trouble with a one of the requirements which is using a drop-down menu to change the time according to a selected time-zone. My understanding is that I need to use the DOM to set the selector values, followed by some simple math for time conversions. Maybe I understand what to do, just not how to do it.
I have been developing a web application which is now a just a basic website coded in html/css/js. I will be shifting it to Rails platform (so I won't really need to implement this answer I am looking for in the long term). Like in Rails (or any other back-end coding platform), we can just define the layout (or template as some may prefer calling it) in one view file and write the other views separately. I was wondering if the same is possible without a working back-end.
Works fine for me in Firefox, Chrome, Edge, and IE11: Demo[^]
The only slight issue is that the changing text size makes it very difficult to hover the next row accurately; as soon as the mouse leaves one row, its text size decreases, and the other rows shift up. It's easier to move in and out of the cells from the side.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
If you don't, already, when refreshing a page under development, use Ctl=F5 (at least in firefox) to force reload without the cache. There are also methods to add a header that forces uncached reloads for all - which at times can be handy.
But the missing "." in both cases was a poor C&P effort by me.
and interestingly noting should have worked - if the code was so flawed - I am increasingly amazed how browser development is progress in holding on to code when it ought to relinquish it - But that the future.
As you will see the problem is solved but the mystery remains!