OK, so...I'm working on my next campaign for my group, and trying to utilize a spreadhseet like table with the accordion to make it more organized than I've had session synopsis in the past.
Here's what i got so far: https://xcomresistance.obsidianportal.com/wikis/mission-reports
And for a single it works fine. However, if i duplicate the box, the code gets all crazy and such as can be seen here: https://xcomresistance.obsidianportal.com/wikis/mission-reports-test
Code follows in seperate posts,
I've never used this Table code beyond some tests and always have to put it as the last thing on the page, otherwise it does this
Am I doing something wrong with the code, the CSS, the accordion, or all of the above.
In other words...HELP!!!!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
Code from good page:
Other Code
CSS for Tables
Looks like both pages actually have the same problem, but the browser only gets confused when the second one is added in.
Just inside the [content] tag, you have a div with a style attribute. The style attribute has an opening double quote, but it doesn't have an ending double quote right after "top:10px;". Add that double quote on and it should start working correctly.
style="position:relative;left:0px;top:10px;
Obsidian Portal Developer
That did it. Thanks. Stupid single error
Sometimes it takes a second set of eyes to spot these things. I must have combed that code a dozen times or more and didnt see that
Oh yeah, happens all the time to me.
The way I found this one was to pull the pieces apart, the contained chunks of HTML like just the table, and then put each contained chunk into an HTML Validator. The Validator will give warnings about things missing like headers and what not because it's expecting an entire html page, but if it says anything about the syntax of specific lines or errors on specific lines, I try to pay attention there and see if I've missed something.
Obsidian Portal Developer
After many CSS code breaks, I've discovered that any time the browser begins displaying the CSS code in the screen, it usually means a bracket wasn't closed off at some point. I did not realize until now that the same issue would arise if an extra bracket was added at the beginning of a block of code! If...nay...WHEN, my code breaks in the future, I'll be sure to look at both the beginning and ending brackets to make sure they are all accounted for. Thanks @thaen and @Keryth987 for giving me a chance to learn the solution to this issue before it inevitably happens to me!