Tournament Brackets [library support]

[affrosponge88]

Just installed the latest version of the plugin and made a test bracket. It came out hard to read, and vertical. Did I do something wrong or are you still working on a fix?


Here's what it looks like:
avclubcommunists.freeforums.net/thread/391/films-2013

[Wormopolis]

it looks normal to me.. what direction did you expect it to go? if it goes horizontal it will stretch your forum way beyond the screen.

[affrosponge88]

Mar 26, 2014 19:01:14 GMT -8 Wormopolis said:

it looks normal to me.. what direction did you expect it to go? if it goes horizontal it will stretch your forum way beyond the screen.

After you said that, I opened up the page in Firefox (I use Safari normally) and noticed that it is not stretched. I'll have to figure out why it's displaying that way in Safari then.

Just for context, to prove I'm not crazy, here's a screencap of how it looks in Safari.

[Wormopolis]

yeah I just checked chrome, firefox, and IE and it looks the same in all of those to me.

I dont have safari to check with it. but I was under the impression chrome and safari use the same engine...

[Wormopolis]

you were going to attach a screenshot?

[affrosponge88]

Mar 26, 2014 20:38:11 GMT -8 Wormopolis said:

you were going to attach a screenshot?

Oh, I'm very sorry to keep you waiting. The screen shot doesn't appear in my last post?

I can post it again here:


Here's a much smaller example. Naturally, if I increase the number of entries, it becomes unreadable (as shown in my last post). For some reason, in Safari, the plugin doesn't want to display any farther than that width it stops at, condensing the entries.

[Wormopolis]

what happens when you hit the collapse button? looks like some CSS is holding the box in a specific width.. like maybe in whatever theme you areviewing? log out and look at that same post as a guest , does it look normal then?

[affrosponge88]

the collapse button simply collapses the it vertically, and the width remains the same. when I log out and look at it as a guest, there is no change.

[Wormopolis]

do you have any other browser to test with? Im not sure why Safari would be doing this.. Chrome doesnt

[affrosponge88]

Yeah, I have Firefox and Chrome as well. And it only does this in Safari. So I can just use those two browsers when viewing the plugin now, it's fine.

[Wormopolis]

I will give you a URL in a little bit to see if it does it there too

[Chris]

I'm seeing the same thing using Safari for windows Wormopolis, it is apparently coming from this CSS rule .posts .post .message table {
width: inherit;
} which is overriding .posts .post table {
 width: 100%;
} (more weight: 3 classes plus a tag vs. 2 classes plus a tag) but this is also true in Firefox and chrome except they have provisions for inherited width (invalid value ?). This appears to be a bug unorthodox value is used system-wide in the Proboards CSS since I am also seeing that very same "inherit" value in the stylesheet on an test forum. In the absence of a declared (valid) width the value should revert to initial value which is "auto" or in the event it nostalgically honors "inherit" then use the computed value of the parent but Safari obviously is having problems with this.

---

forgot to offer one possible solution

.posts .post .message table.TBtourneyOuterTable {
 width: 100%;
}

[Wormopolis]

I was waiting to get home before putting some default CSS in there to control width. I just couldnt see it without having safari myself. and I always thought safari and chrome yielded the same results.

[Chris]

Apr 3, 2013 21:00:00 GMT -8 Google forks WebKit, promises faster, leaner Chrome engine said:

Google has announced that its Chrome browser is dropping the popular WebKit browser engine in favor of Blink, a new fork of the code that the Chocolate Factory says will make Chrome faster, more powerful, and more secure.

The internet ad giant announced the move on Wednesday via the official blog of the Chromium project, the open source effort upon which Chrome is based.

"This was not an easy decision," Google's Adam Barth wrote. "We know that the introduction of a new rendering engine can have significant implications for the web."

"Nevertheless, we believe that having multiple rendering engines – similar to having multiple browsers – will spur innovation and over time improve the health of the entire open web ecosystem."

Past versions of Chrome have rendered web content using WebKit, the same open source rendering engine that powers Apple's Safari and various other desktop and mobile browsers.

But Chrome never used WebKit in quite the same way that Safari did. For example, Chrome ignored WebKit's JavaScriptCore component in favor of Google's homegrown JavaScript engine, V8. It also handled multiple browser processes in a significantly different way than Safari did.

The need to maintain a WebKit code base that worked with Chrome's approach as well as those of other browsers has made both the WebKit and the Chromium projects increasingly complex to manage, Barth said, which in turn has slowed down the pace of development.

By breaking with the mainline WebKit project and developing Blink as a separate effort, Google aims to improve Chrome more rapidly while allowing Safari and other WebKit-based browsers to do the same.

[...more]

[Wormopolis]

awww.. now i have to download safari...