BETA SENIOR MEMBERS - Post Comments and Bugs Here

All WebmasterWorld Beta Site Discussions Must Be Posted Here

[incrediBILL]

NOTICE:
By accessing the site you are agreeing to keep the privileged beta confidential, and any discussion, screenshots, retransmission, is permitted within the allocated beta discussion threads only. If you cannot agree to these terms, do not access the beta test, and simply wait until it becomes public.

Anyone that feels they cannot abide by these terms should simply not access the beta website and wait until it becomes public.

---

To avoid confusion for other members; all WebmasterWorld Beta discussions must be restricted to this thread only.

Report any comments, bugs, feature requests, etc. in this thread. We may open up additional threads for specific topics but those too will be restricted to Senior Members only.

We hope you enjoy the new site and look forward to all your comments.

To see what's new, go here: [webmasterworld.com...]

To see the new site, go here: [webmasterworld.com...]

You will need both your WebmasterWorld login plus the Apache user name and password to gain access to the beta site. For some reason a couple of people were unable to get Apache authorization. If authorization fails, we apologize but we don't know what's causing it and can't fix it at this time. It must stay in place to keep crawlers out of the new site.

[Fotiman]

When viewport width: drops below 1216
Top menu items go from:
Free Tools, Control Panel, Pro Membership, Recent Posts, Open Posts, Resources, Logout
to:
Free Tools, Control Panel, Pro Membership, More
The "More" dropdown then contains:
Recent Posts, Open Posts, Help, Library, Announcements (note that Help, Library, and Announcements are in the Resources drop down).

So the Logout link goes missing.

[Fotiman]

When viewport width is between 1216 and 1245, the Search box gets pushed down to the next line.

[Fotiman]

When the viewport width drops below 1008
Top menu items go from:
Free Tools, Control Panel, Pro Membership, More
to:
Free Tools, Control Panel, More
The "More" dropdown then contains:
Recent Posts, Open Posts, Pro Membership, Help, Library, Announcements

So the Pro Membership appears AFTER Recent Posts and Open Posts, where previously it was BEFORE those.

[Fotiman]

When vieport width is between 784 and 1007, the Search box seems to disappear entirely. At smaller width, the Search box returns under a Hamburger menu.

[Fotiman]

When viewed on my phone, there still appears to be whitespace along the left and right of the page. That's space that could probably be turned into usable space at that small of a screen. As a result, the breadcrumbs just for this page take up 3 lines and look like:

 Home / Forums Index
 / Local / WebmasterWorld Community
 Center

[Fotiman]

My post on Msg# 4739694 contained quote, pre, code wrapper. Also, the first word, Home, seems to have been bolded? What changes have been made to these tags?

This is a quote

This is pre

This is code

This is quote, pre, code

This is pre, code

Note, for the longest time I've wrapped my code examples in quote, pre, code, so changing these tags may have a broad impact on how code is displayed within the site.

[tangor]

Usually surf with NoScript, thus the googleapis are off. Beta Site works pretty well that way, though none of the top drop downs worked. Like the new look btw... that said, I don''t like that clicking top menu items opens a new tab in my browser instead of displaying the result in the same window. Ended up with 5 tabs open before I clicked BACK and nothing happened (duh!)

I did turn on goggleapis since I could not find RECENT posts without it. Not sure I like that, though can probably do what I have in the past: Bookmark that page as my "home" page, which is what I have done for years.

Only remark is that new tabs whether I want them or not...

[Fotiman]

The forum index pages (like [webmasterworld.com...] have borders on the table columns and rows that are a bit much. They're really distracting, and break up the page so much that it becomes harder to read. Removing the borders between columns might make it easier to read and less spreadsheet-like.

[Fotiman]

The floating link on the right side of the page to the #top does not work (but the #bottom link does).

[incrediBILL]

The floating link on the right side of the page to the #top does not work (but the #bottom link does).

Works for me all but a couple of pages, haven't figured out what breaks it on others.

FYI, it's possible it may not work at all on Macs as we did some testing and links to named anchors don't seem to work at all.

So a link to something like "example.com#top" doesn't work at all. We tested this on WebmasterWorld classic using Windows, Android and a Mac, Windows worked, Mac's didn't, and we tried Safari and Firefox, don't remember if we did chrome. So that may be the reason those buttons aren't working but I can probably make it work on all platforms using jQuery.

[Fotiman]

The new dropdown on the Msg# is great, but apparently not done. Copy Link, and all of the social links don't work.

[Fotiman]

Regarding the #top link... I'm using Win 8.1, Chrome. When I inspect the #top anchor, the computed styles for it look like this:

background-color: rgba(0, 0, 0, 0);
box-sizing: border-box;
color: rgb(0, 0, 0);
display: inline;
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-size: 14px;
height: auto;
line-height: 20px;
text-decoration: underline;
width: auto;

When I inspect the #bottom anchor, the computed styles look like this:

-webkit-background-clip: border-box;
-webkit-background-origin: padding-box;
-webkit-background-size: auto;
background-attachment: scroll;
background-clip: border-box;
background-color: rgba(0, 0, 0, 0);
background-image: none;
background-origin: padding-box;
background-size: auto;
box-sizing: border-box;
color: rgb(255, 255, 255);
display: inline;
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-size: 14px;
height: auto;
line-height: 20px;
padding-bottom: 2px;
padding-left: 2px;
padding-right: 2px;
padding-top: 2px;
text-decoration: underline;
width: auto;

Note, your #bottom anchor has an inline style attribute (which you should remove) that contains some invalid values:
margin:none
padding: none
background-color: none
none is not a valid value for any of those.

I'm not sure why the computed style on the #bottom link contains so many more properties. Perhaps because the <body> is not a direct parent like it is for #top? It is picking up some styles from custome-styles.css that the #top anchor doesn't. Whereas the #top anchor is totally empty and doesn't take up any pixel space at all, I suspect that #bottom does (because it has 2px of padding, etc.), and perhaps that's the difference? Not sure. But hopefully this gives you some place to start.

Side note, instead of using named anchors, consider using an id attribute instead, as that's the recommended way to add anchors now.

[Marshall]

On the Recent Posts page, it states at the top "showing 1-25 of 59" but I did not see any link for going to page 2 on the bottom right where it always was, or anywhere else for that matter.

Marshall

[netmeg]

I quite like it. I haven't put it through its paces yet, but it's very readable.

Those columns on the left are gonna drive me batty, though. Kind of wish they were optional.

[stever]

Generally good job from what I have noticed so far.

As I thought it might, the Recent Posts table breaks responsive width on smartphone sizes. (Tables are tough!) Possibly changing (or removing via a media query?) the needlessly long time display and generally unnecessary post total columns would help?

[stever]

In the beta version, Featured threads adds an additional invalid slash and directory to the link:
[webmasterworld.com...]

[stever]

In the 'Message Accepted' message box there is a random charset text snippet at the top of the box.

Like so: Content-type: text/html;charset=ISO-8859-1

[wilderness]

FWIW, I've browsed through the Beta pages with some minimal viewing.
On the surface it appears functional.

My only personal negative is that individual responses within a thread are implemented via Java Script with the pull downs.

I personally navigate Webmaster World (and most other websites) with Java Script turned off, thus I'll never see (or be able to use) the pull down menus.

[netmeg]

Personally, I'd probably rather have the ability to mark my 'favorite' threads and pin them to the top (just for me) or sort that way, but that's just me.

[Fotiman]

+1 to what netmeg said.

netmeg, if you use Chrome, I wrote a browser extension that lets you do that (though, it would be ideal if something like that was built into the site instead). My extension may need an update for the new site, though.

[incrediBILL]

Personally, I'd probably rather have the ability to mark my 'favorite' threads and pin them to the top (just for me) or sort that way, but that's just me.

That's what FLAGS are for, in the current WebmasterWorld classic.

I'll be adding that link back into WebmasterWorld beta real soon, but that's how you track all your favorite threads and the flags show alongside your thread, in beta there's a column just for the flag icons to make it super simple to see them all.

However, there's no way to pin your flags to the top and I don't think you would really want that as eventually you would have a forum clogged with flags and all the new content would be way down the list, lots of scrolling.

However, I might be able to slip in a link to either sort by flags so you could toggle it on/off or one to just show the flagged posts in that forum, vs. showing all flagged posts which is currently how "my flags" works.

So now that you know this, go flag something in classic for the moment and see how it works in the beta.

I'll go get that flag link back to active. It's all wrapped up on one last little thing I'm working on that will be online real quick.

[Fotiman]

Sorry, I read that quickly. Flags isn't what I meant. I want to pin specific FORUMS, not threads. I want a list of my favorite forums at the top of the forum index page.

[netmeg]

Oh that too. But no, I originally meant threads. Why call 'em flags when they're favorites everywhere else on the planet? Ok though, I'll look at them. Never having had them explained to me, I thought that meant something else entirely. But yah, if we can't pin, being able to sort would be good.

[netmeg]

(In my *ideal* world, I'd take what Fotiman said one step further and let me construct a 'dashboard' of my favorite forums in the order in which I care to read them)

[incrediBILL]

Why call 'em flags when they're favorites everywhere else on the planet?

Because we had flags years before anyone else had favorites.

Maybe we should rename it, might make sense.

Where do you see favorites besides Twitter?

I need a list to make a case for renaming ;)

[incrediBILL]

Side note, instead of using named anchors, consider using an id attribute instead, as that's the recommended way to add anchors now.

Maybe I'll add the ID as well since that might be what the iStuff is looking for.

Not sure why you care what other styles are on those anchors and they just inherit whatever is in play wherever they're inserted which really shouldn't impact how they perform, but if they were visible it would matter a whole bunch.

[netmeg]

Where do you see favorites besides Twitter?

Windows (I dunno about Macs, I don't use 'em)
Ecommerce platforms and websites that aren't Amazon
Bookmark programs
Video platforms (such as YouTube and Hulu)

Probly a lot more.

[Fotiman]

Not sure why you care what other styles are on those anchors

*I* don't care about them, I'm just wondering if the visibility has some affect that causes the browser to not scroll to it. That is, I would expect it to work as it is, just noting the differences in how the browser "sees" those two anchors.

[Fotiman]

When the "top" anchor has no content, if I right click on it in the Chrome Developer Tools (the Elements tab) and select "Scroll into view", nothing happens. However, if I edit that anchor to have some content, then "Scroll into view" works, and so does the link to the top.