May 26, 2016 at 2:30 pm #40362
Since the implementation of the new site design, I am unable to post and reply when using Internet Explorer 11.
The text boxes are simply not showing.
Anyone else seeing this?
Update Versions 11.0.31 (KB3154070)
Windows 10 Enterprise 1511 10586 318
May 26, 2016 at 2:35 pm #40366
May 26, 2016 at 2:39 pm #40369
For reference, this is what I see when looking at this thread in IE 11:
May 26, 2016 at 2:54 pm #40371
Interesting. I've no idea whatsoever why it would do that. Let me spin up a VM and see what I can figure out. Meantime, please do make sure you're not running any blockers or filters that might be causing it.
May 26, 2016 at 2:58 pm #40378
Confirming that Edge works for me. Wow, they _really_ want you to use Edge, too. Still trying to find IE11.
May 26, 2016 at 3:03 pm #40383
If you look at the page source, you should be able to search for:
[div class="bbp-reply-form" id="new-reply-40362"][form name="new-post" id="new-post" action="https://powershell.org/forums/topic/unable-to-post-reply-when-using-internet-explorer-11/" method="post"]
(I've replaced angle brackets with square brackets so they'll render here). Can you confirm that you're seeing this in the page source? It's the reply form. I realize IE11 isn't rendering it, but want to make sure you're seeing the same source HTML that I am.
May 26, 2016 at 3:14 pm #40385
Nope ... from the looks of it, that is not in the source.
I just checked from another computer as well (same versions), and the problem shows there as well.
May 26, 2016 at 3:15 pm #40387
Guys, I've no clue. I'm seeing the reply form in the raw HTML, and IE11's inspector isn't showing any CSS style that's preventing it from displaying. In fact, the inspector is showing the reply form area as having a visible size on the page, but it clearly isn't rendering. I've lodged a support request with the theme developer to see if they have any advice. Meantime, all I can suggest is using another browser.
May 26, 2016 at 3:20 pm #40391
That's super-odd. Because I'm definitely seeing it in the source on IE 11. Can you triple-check? Maybe enable Developer Tools (F12) and use the Inspector?
May 26, 2016 at 3:21 pm #40394
Will do ... thanks Don
May 26, 2016 at 3:25 pm #40396
Just checked again, and you are right ... it does show in the source.
Sorry about that.
May 26, 2016 at 3:34 pm #40400
Just experimented turning off our caching and optimization plugins, and it had no effect. I'm chalking this up to an IE quirk or bug; we'll see what our theme developer has to offer in way of advice. Sorry guys... hopefully Chrome or Edge is a viable workaround until it's resolved.
May 26, 2016 at 4:01 pm #40404
No worries ... hope a solution can be found, but will use alternative browsers until then 🙂
May 26, 2016 at 7:27 pm #40414
well IE 11 isn't working but there's a workaround.
Add powershell.org to the list of URLs in the Compatible view Settings and Voila, you have the missing section up.
Its how I'm writing this comment.
I dont use IE 11 on win 10 as I prefer Edge which is why I initially didn't notice this happening on IE 11 as well
Now to try and work this on my phone.
by the way note that the site looks a bit messy with compatible view on but at least you can post 😉
May 26, 2016 at 7:30 pm #40419
Arie, any idea exactly what "Compatible" does differently? That might clue me in to what's actually wrong.
May 26, 2016 at 8:40 pm #40440
Introducing the Compatibility View List
Web authors use doctype directives to specify whether their webpages should be displayed in standards mode or a compatibility mode called "quirks mode." Internet Explorer 9 provides a new standards mode that supports industry standards more completely than the standards modes of earlier versions. By default, Internet Explorer 9 uses IE9 mode to display standards mode webpages. For pages built to support the features of earlier versions of the browser, this can affect what the user sees when the page is displayed. For example, pages that displayed properly in IE7 Standards mode may appear differently when displayed in IE9 mode.
Understanding Compatibility View
When a standards-based webpage is displayed in Compatibility View, the following changes occur:
•Pages are displayed in a mode determined to be appropriate for the site, generally IE7 mode.
•In the user-agent string, the browser identifies itself according to the document mode used to display the site. For example, if the site is displayed in IE7 mode, then the user-agent string contains MSIE 7.0 instead of MSIE 9.0.
•Conditional comments and version vectors recognize the browser as a browser corresponding to the selected document mode. For example, if the site is displayed in IE7 mode, the version vector will be reported as Internet Explorer 7, rather than IE9 mode.
These changes help ensure that users can still use websites that do not fully support the current versions of established and emerging standards.
I remember reading somewhere that for Edge to avoid issues, the User-Agent it presents to website is actually FireFox so any conditional code that checked for IE will not happen and the real web site would be shown, instead of a special costumed alternate site that "regular" IE get. Might not be fully accurate information or has been changed since but I have no doubt that's one of the reasons why its not showing on a normal IE without the
May 26, 2016 at 9:15 pm #40450
its chrome and safari actually as its not using the old Trident HTML engine
This is the User-Agent that Edge passes
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586
naturally any IE-detecting mechanisms will not see it as "another IE"
Using Developer Tools on IE 11 and on Edge, the full HTML is equal in both so everything is getting to the browser, its simply not rendered and I cant see anything wrong in the html or the visible parts of CSS
May 26, 2016 at 9:33 pm #40453
Seems using FieldSet and Legend have been notorious issues for IE and CSS coders.
Wont be surprised if still exists in IE11 since then.
the new-post form element opens a new Fieldset class and a Legend as the first title of the fieldset
the entire fieldset is the missing part that cant be seen in IE11 although you can see it in the html itself.
Who needs IE 😉
May 27, 2016 at 7:01 am #40541
Who needs IE ... well ... I do – It's the the corporate standard browser here 🙂
May 26, 2016 at 9:41 pm #40458
You mentioning the site being Responsive and the comment in the last link about the viewpoint being 320px wide because of it, having difficult issues with long titles, reminded me of another issue on the phone version IE that ill just mention. not expecting a solution as its quite obvious not going to change the lacking IE version.
The blue headers across the top of the site, with Welcome or the name of the forums, when viewed on the phone browser, doesn't scale its font size, so you get almost a full screen covered with the blue bar and the characters of the name, broken into parts.
I suspect another problem with how mobile IE renders. As IE11 is ok in that field.
June 12, 2016 at 8:34 pm #42636
I've made a change to the theme style suggested by its developer; can someone from this thread check IE11 and let me know if it's made a difference?
June 13, 2016 at 12:25 pm #42699
June 22, 2016 at 8:50 pm #44462
Works for me as well – thanks for fixing this.
You must be logged in to reply to this topic.