I was reading some reviews you did, and it's possible they fell short of the length. Moderators have to approve the thread first by checking that you did 3 reviews that met the criteria. I'd possibly PM a moderator in that section of the forum and see what's up.
To be honest, I'd guess the reviews were too short (I believe it's 2 PARAGRAPHS minimum), but I could be wrong.
Also, I don't know if any of you are familiar with the review forums, but I tried posting there twice, after doing 3 reviews, and after submitting the new thread, it went to the forum again. My thread was not there and when I checked my latest threads, the thread wasn't it that list either. Any idea why this is occurring?
Review requests go into a moderation queue to be vetted by Advisors so that they meet the requirements. Once approved they will appear in the forum but may take a couple of days depending on what else is there . (I've approved it now anyway so you should be able to see it.)
oh okay. fixed fixes the object in the same place on the screen while absolute fixes in the sample place in the layout?
Fixed relates to the viewport. Your coordinates are based off the corners of the screen itself, not the web page or content inside. Scrolling doesn't change where the viewport is, so the element doesn't move.
Absolute relates to whoever the nearest positioned ancestor is; if there isn't one, the viewport (the specs say "otherwise the viewport" but really, it's the top of the document. Which is why the abso-po'd element can scroll offscreen).
A positioned ancestor is any parent element (or grandparent or great-grandparent) who has either position: relative or position: absolute set on them.
So sometimes you see an element with position: relative on it, but no coordinates like left or top. Likely, they either wanted to absolutely position a child (the top left corner of the position: relative element is 0,0 to the abso-po child)... or they wanted to set a z-index. Otherwise, they were probably just wasting code for no reason :)