joshjull
Registered User
The migration has made it no longer necessary to cap off threads at about 1000 post.
Is there a larger cap, or no cap at all?
The migration has made it no longer necessary to cap off threads at about 1000 post.
As I understand it there is no cap.
Heh, sounds about right. They tinkering with tweet iframes? Ever since I logged in this afternoon, I'm seeing plenty of new white space in regards to tweet embeds, as their individual iframes appear to be defaulting to a 500px min-height parameter despite their short length, resulting in a needless 300+px of white space in applicable posts.Ad Code is updated. The issue with ad blockers not working with chrome is fixed. Clear cookies/cache, reboot chrome and ad blocker will work when you log in. You'll need it because I can't get them to remove blood sucking Starbucks ads.
Sill hoping to get a reply to this.I have a problem.
The default text is Arial and I have to change it to Verdana each time I post.
Heh, sounds about right. They tinkering with tweet iframes? Ever since I logged in this afternoon, I'm seeing plenty of new white space in regards to tweet embeds, as their individual iframes appear to be defaulting to a 500px min-height parameter despite their short length, resulting in a needless 300+px of white space in applicable posts.
<iframe data-s9e-mediaembed="twitter" allowfullscreen="" onload="var a=Math.random();window.addEventListener('message',function(b){if(b.data.id==a)style.height=b.data.height+'px'});contentWindow.postMessage('s9e:'+a,'https://s9e.github.io')" scrolling="no" src="https://s9e.github.io/iframe/twitter.min.html#{$id}" style="background:url(https://abs.twimg.com/favicons/favicon.ico) no-repeat 50% 50%;border:0;height:186px;max-width:500px;width:100%"></iframe>
It edits in Arial and posts in Verdana automatically. You don't have to manually change it. Presumably that's to let you know you're still composing your post.Sill hoping to get a reply to this.
Can I be the only one who has this problem?
I take it the advanced options when replying or making a post are gone completely?
I still get the ads that redirect away from the site to the scummy "congratulations you're the 1,000th visiter click here for a free ipad" garbage on my phone, and the only way to get out is to close the tab or hit the back button a dozen times. **** like that shouldn't be a part of any reputable site its really starting to piss me off.
Sweet baby Jesus I no longer have to disable Java and I can see tweets. This is much better. Slowly getting back to a great site again.Ad Code is updated. The issue with ad blockers not working with chrome is fixed. Clear cookies/cache, reboot chrome and ad blocker will work when you log in. You'll need it because I can't get them to remove blood sucking Starbucks ads.
Thanks, I'll take a screen shot and report it next time it happens. It only happens while browsing this site, and goes away like all the other ads when I turn Javascript off.Reports about bad ads must be reported in the Support Forum. That one might be malware coming from an app. I'll bring it to websupport's attention if it's reported properly.
They should include as much as possible of the following:
1. Location/Country
2. Device
3. Browser
4. Company/product of ad.
5. A screen shot if possible,
6. Brief description of how the ad is a problem.
7. Page/Pages affected
How to take screenshots:
Android devices - power button + vol down
iOS - power button + home screen button
Desktop - browser addons can be used with Chrome and Firefox, Moo0 Screenshot can be used with anything
Windows 10 : windows key + print screen
The More Options button = Advanced Reply
Thank you.It edits in Arial and posts in Verdana automatically. You don't have to manually change it. Presumably that's to let you know you're still composing your post.
It's not a problem, it's a feature.
Odd. I never experienced cut-off tweets on any browser or device. I only noticed the change or workaround, so idk what conditions were producing that. After a quick glance, I'd probably first suggest replacing "height:186px;" (or the "height:500px;" I'm seeing now in the page source) with "max-height:none;" so that it adds the correct height into the style. That works in the dev console, at least, for both text and mediacard tweets and trims away the 300+px and 60px padding respectively.See if you can figure it out -
HTML:<iframe data-s9e-mediaembed="twitter" allowfullscreen="" onload="var a=Math.random();window.addEventListener('message',function(b){if(b.data.id==a)style.height=b.data.height+'px'});contentWindow.postMessage('s9e:'+a,'https://s9e.github.io')" scrolling="no" src="https://s9e.github.io/iframe/twitter.min.html#{$id}" style="background:url(https://abs.twimg.com/favicons/favicon.ico) no-repeat 50% 50%;border:0;height:186px;max-width:500px;width:100%"></iframe>
Embeds were being cut off at 186px. It's supposed to add data height. Work around :
height:186px changed to height:500px to show full tweet. Need to figure out why data height isn't being added or rewrite code to auto-size it all.
It occurs with chrome. I'm sure it's caused by instart logic. Your fix didn't work. Instart logic detects when dev console opens and disables itself.Odd. I never experienced cut-off tweets on any browser or device. I only noticed the change or workaround, so idk what conditions were producing that. After a quick glance, I'd probably first suggest replacing "height:186px;" (or the "height:500px;" I'm seeing now in the page source) with "max-height:none;" so that it adds the correct height into the style. That works in the dev console, at least, for both text and mediacard tweets and trims away the 300+px and 60px padding respectively.