New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webview doesn't render and support deviceEmulation #5488
Comments
|
I'm closing this since it is an expected behavior of Chromium, and we are not able to change this on Electron's side, if you would like to change this I suggest creating an issue at Chromium's issues list. |
@soulteary Consider NW.js which supports deviceEmulation. |
@deepak1556 @zcbenz thx. |
@GnorTech Thanks for answering this issue, even though you didn't actually read it. Please allow me to share you some experience on how to promote an open source project, since you are trying hard to do that. One of the keys is issues management, you need to answer every issue, categorize them, and close them when they are resolved, so people can trust your project and are confident to contribute to it. I'm not saying you do not understand that, it is just amusing that you spend more time answering issues in Electron instead of NW.js, while trying to persuade people to use the latter. |
@zcbenz I do read the requirement. I'm just helping @soulteary and give him a way out with a feature in NW which you don't want to support. I don't see any problem in it. Promoting NW is just a side effect. If you're curious on my role in NW, unfortunately that doesn't include issue scrubbing. My work has been focused on helping Chromium rebase so that NW could release after Chromium upgrade soon. |
@GnorTech No you didn't, if you really read it you will find out it is not about |
Hey @zcbenz the issue is about webview and the device emulation, as OP said btw, NW's webview has more features than the one in Chromium, you probably didn't know it. |
Hey @GnorTech / @zcbenz , thank you again, both of you're nice and plz take it easy. ** SORRY FOR MY POOR ENGLISH 😁 ** You're right but no all, is my fault, i should describe more clearly. I'm trying to make a software, aimed at helping front-end coders to test GUI and users action on web page easier, just like someone suggest that electron may able to. The web page running in standard browser/any kind of webview. I've tried these way to collect user action:
They work find at most scenes, but i'm trying to record case by case, there're so many case need to managed. Because developer's testing target in different network environment as usual, replay user action in server by casper.js/phantomjs is a way but not a wise choice. Because browser plugin api possible changes with browser release new version, and it often update, it won't be a reliable base for replay or manage test case which record by developer. So, make browsers or use browser like container(just like electron or node-webkit) is better way to help me finish the job. that's all my demands. But when i try to use electron to record my test case, i found it's We know that two heads are better than one. Both electron and nw.js are great one, it is not necessary to quarrel or angry. Maybe we should seeking common ground while putting aside differences. |
how to emulate mobile page in electron ? |
so the answer is no? |
i have the same question, but no idea........ |
Hi, I've some problem with electron on devtools(both BrowserWindow and webview)/deviceEmulation.
I use
<webview>
tag to load url which page i wanna test.If i use
enableDeviceEmulation
inBrowserWindow
, the<webview>
wouldn't render any content, unless i open BrowserWindow's devtools and click[toggle device mode]
.Code here:
Then i remove above code. Just wait webview
dom-ready
, and open webview's devtools , i found the devtools doesn't containtoggle device mode
button, and i can'tenableDeviceEmulation
inwebview
.I found if i detach the BrowserWindow's devtools window, it's toggle device button will miss as the same, but it seems no way to dock the webview's devtools window...
The text was updated successfully, but these errors were encountered: