@Nirzar do you want this to basically look like Opera Mini compressed?

@dr0ptp4kt ideally, yes.

Wouldn't this be fixed automatically if we serve the same version to UC Mini as Opera Mini? Right now UC Mini uses the Javascript version right?

@Nirzar, I'm not sure about the root cause. UC Mini applies a number of techniques. @Peter would you happen to know off the top of your head how UC Mini is treated in the ResourceLoader / NORLQ / <noscript> context?

@dr0ptp4kt I don't know but my guess it is not, but we should check. I'm thinking that we miss the search button either is that UC Mini strips away that for us (is that likely?) or we send the Javascript version.

@ovasileva @Nirzar @phuedx We determined that this needs more investigation before we can tackle it. Can you come up with a spike to review what's possible and what the approach could be?

I've spun off T146699 as part of my investigations so far which is part of the problem and I've also captured T146703.

Useful things that I've learned so far:

• UC Mini Browser cannot handle async JS loading. As a result the startup module never loads but the inline script removes the client-nojs class - so the page gets stuck in a limbo state.
• The user agent is rather unhelpfully "Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv: 1.2.3.4) Gecko/"
• UC Mini browser doesn't support landscape mode
• Debugging in uc mini browser is hard. No support for console.log or window.alert ... I had to use document.title and document.write (eek). Cache clearing is needed after every page view.

I think this can be continued in T136803 - this work touches the performance team's stack so it would be good to get a sense from them what can be done to fix this.

@Jdlrobson I think you meant "UC Mini Browser" when you wrote "UC Browser", right? For documentation purposes it would also be good if you could mention the browser version and the OS it's running on.

Yup. I've corrected. Thanks for pointing that out. Most of the actionable information is captured however in T146699.

Would it be fair to retitle this task to something like the following: "Is it possible to search from the UC Mini browser?"

I think that T146699: Browsers that do not support async JS do not degrade gracefully answers the question @Jdlrobson. Neato!

@Jdlrobson why is this task in sign off? Your last comment says you're investigating.

@bmansurov sorry the outcome is T147369. It was not async that was the problem. It just cannot handle a lot of the JS we run.