Happy New Year to All!
Any thoughts or hard/anecdotal evidence of one browser being less buggy or faster? We have relied on Chrome since our inception… I’m considering trying out Firefox as some of our Epicor tickets have stated they’ve seen “fewer issues” in Firefox with some of them (for instance, with column sorting issues).
I’m open to hear your experiences…
We use Edge since it works better with Microsoft Entra. The browser picks up their linked account in Windows and does not require them to enter their password again when logging into Kinetic.
I have tried Chrome a few times and haven’t noticed any difference. I haven’t tried Firefox.
Epicor states that Chromium (Chrome, Edge) and Safari browsers are supported.
MOST LIKELY, if you’re not doing a lot of customization or wonky stuff for the screens, any browser would PROBABLY suffice.
The more fun stuff you want/need/like to do in Application Studio, the more likely you probably are to find out why the other browsers aren’t supported.
Just sayin’
Guess I’m in trouble
We all have different ways of passing the time of day.
And then there was:
This reminds me of the Gopher Protocol we used to use for browsing Library holdings at Universities… I Don’t remember Lynx, but I remember Mosiac… I’m old, but not ancient yet… give it another decade 
!!!
I’ve been using firefox mostly. That’s from a personal preference for browser controllability. I’ve been working in various chromium browsers as well, like Edge and Chrome. Not Safari though, we have but one user who only rarely uses a Scottish laptop and that won’t increase.
Of course I already tried eww! Lynx will end the same way:
Can confirm though, this forum here is readable in eww. Readonly without javascript, but readable nonetheless.
We “standardized” on Edge… but its not infallible.
We’ve seen some glitches where things don’t appear or work correctly… and I’ve asked the user to switch over to chrome and try it, and it’ll work.
I’ve also seen the inverse… things not behaving in Chrome… switch to edge and its fine. Not sure if these are browser cache issues or not… but they do tend to rear their heads after updates.
One example I can remember is, our Engineers enter time directly via Time Entry menu. I had one user who couldn’t toggle their calendar between weekly and monthly. Switch browsers… can do it just fine. Cleared their cache… still didn’t work in browser A. So they just use Browser B when they’re entering time. Very odd behavior. Some time later it just starts working for them in both Browsers. Again, can’t put my finger on the cause. But… I guess just a PSA… mixed results. I couldn’t say one is significantly better than another. But if an issue arises, I would recommend testing in Browser B and see if the issue is browser specific or not.
I was just trying to figure out how to say this… and you gave me a GREAT opening. thanks!
EVERY browser, including the Elect Few, is going to have (ahem) fallibilities. The issue I have with the non-Elect Few is that I can’t report those fallibilities to Support… they’ll say, “please try it in one of the Elect Few”.
Whether or not it truly IS a problem, that time I now have to spend reproducing the issue is just wasted time.
All too familiar. If using Chrome, try Edge. If using Edge, try Chrome. And what if you can’t reproduce the issue…but get different issues in each browser? Frustrating consumption of time that would be better spent elsewhere.
Please submit an Idea.
An idea for what though? If support says they can’t find a root cause for something unless it can be repeated at will…
Any breaking compatibility issues will be javascript. Namely, using things that only exist where web devs are consistently testing, which is chromium on 1080p. Most of the web client depends on competent third party libraries, which enforces compatibility. Code copied from stackoverflow and copilot tends to trail the bleeding edge enough for incompatibilities to be patched, and that accounts for 99.9% of what’s left of web development (this comment is not specific to Epicor…).
Cache dependency and management is what I see being more relevant. The statelessness / lazy load deep end is moving faster than client development can keep up (waves broadly at grid references) so it’s extremely useful to be able to properly nuke a session and start from scratch.
Lots of ways to do that. The most accessible is incognito. This is what I recommend. Every web client session should be incognito. Closing an incognito session deletes the relevant cache. Some users get self conscious about incognito mode because of reasons, but they can adjust.
Chrome and Edge are only incognito-ish. Especially so if a user is logged in to the browser. I don’t think it’s bad enough to be a problem, though.
Interesting idea…will pass that along next time someone squawks about their browser getting squirrely.
You can create shortcuts that launch Kinetic using Incognito or InPrivate by adding the appropriate arguments so users don’t have to remember to get there. Not a bad idea to have this separate from other browsing. Also, this should block all plug-ins/extensions to guard against malicious ones.
start msedge.exe -inprivate
or
start chrome –incognito
Exactly! But that is a response that is given too often.
Yup…we’ve been live for less than 2 years and I’ve heard it enough already. Sometimes I wonder if they think I’m opening support cases just for spits and giggles.