Here’s another really weird bug with the Modern Web Browser control that was mentioned to me by Juanfran Rodriguez (@juanfranrodriguez), one of my YouTube viewers.
The issue is that if you use a capitalized the file extension used in the Modern Web Browser control’s Control Source, when trying to directly display media, you will get gibberish displayed rather than the actual media.
Since I’m on the subject of Event bugs…
It only makes sense to mention another longstanding bug when renaming controls! One that I was reminded of by a recent comment on my YouTube channel by Xavier Batlle (@xavierbatlle1828)
I know, this isn’t anything new, but I still view it as a bug. Why is it if I Cut a control on a form to go and paste it in the same form elsewhere, we loose any associated events? The code remains in the Form module (VBE), just the event property value of [Event Procedure] are lost.
After my recent article regarding the Modern Web Browser control always appearing when placed on a tab control:
I decided to do a little more testing, as this was one thing I had never explored before, well not with the Modern Web Browser control at least.
Sadly, things went downhill!
A small UX bug in MS365 in which on the Ribbon for Form Design the Tab Control icon is sideways???
Well, there’s yet another issue with the Modern Web Browser control!
This is one I didn’t find myself, but that one of my viewers brought to my attention via my YouTube channel.
A short while ago, about a month ago, I made a posting about one of my Feedback Portal suggestions being deleted without a trace:
I’ve really been trying hard lately! Truly have. I been trying to be that positive guy, try to keep pushing forward with the Feedback Portal, ignoring all the issues, hoping that perhaps some of it would filter through to the Dev Team. Recommending we all continue to contribute that it would show engagement and force Microsoft’s to reciprocate.
BUT, it’s happened again! Another suggestion has vanished!
If I’ve said it once, I’ve said it a thousand times, the Modern Web Browser Control (MWBC) is simply not a finished product, not nearly tested properly.
Here’s yet another issue with it!
I’ve been trying, in vain, to migrate an HTML page that references web based resources (JS, CSS) to instead use local versions. This is super simple to achieve with traditional browsers, however proving to be a nightmare with the MWBC!
Normally, you simply update the HTML page from
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js" integrity="sha512-v2CJ7UaYy4JwqLDIrZUI/4hqeoQieOmAZNXBeQyjo21dadnwR+8ZaIJVT8EE2iyI61OV8e6M8PP2/4hpQINQ/g==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>
to
<script src="../js/jquery.min.js"></script>
Easy, right!
However, things quickly fall apart with the MWBC!!! (AGAIN)
Ever made a mistake?!
It happens.
Say, you input the control source of a Modern Web Browser Control (MWBC) as a local html file, but you make a mistake in the path or file name, so in fact the specified path/filename doesn’t exist.
Ordinarily, in Edge, you get a nice screen that clearly indicates:
File not found
It may have been moved, editied, or deleted.
ERR_FILE_NOT_FOUND
Furthermore, if you open the inspection tools and switch over to the console you’ll see a clear message:
Not allowed to load resource:
file://YourFileName
Found another bug with the Modern Web Browser Control (MWBC).
If we look at the Property Sheet for a MWBC, we get:
