I have installed MAMP V 3.5 today on Macbook Air, OS X El Capital, V 10.11.2 When I launch the application, the Server shows it is connected to Apache, but the web browser (Safari V.9) fails to open the page. the URL reads
http://localhost/MAMP/?language=English
Safari doesn't work for me, even though it's my browser of choice.
Try Chrome, and make sure you type: localhost:8888/
(or whatever port number you choose, if not the default)
Hope that helps.
Tyler
Related
I am using a Mac Book Pro with M1 chip, and my MacOS is Ventura 13.0.1.
I have installed live server on vs code, but when I open (run) the live server the safari browser doesn't open.
Extension version: 5.7.9
VS Code version: Code 1.74.0 (Universal) (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:43:37.594Z)
OS version: Darwin arm64 22.1.0
I have tried almost everything that exists in Internet, but nothing makes it run.
So, I have a index.html file, under a folder names starter, I right click the file and select the "Open with Live Server" option.
A new page in Safari opens (unter the 127.0.0.1 and the available port) but it never loads.
The same thing happens if I start live server (Go Live) from vs code button that exists in the status bar. Safari is opening the page but it never loads.
I would expect for the Safari page to open and see the folder that my index.html file is lying. I would also expect after the Safari page has opened, after selecting the "Show Javascript console" in the browser and after choosing my .js code to automatically show me the result of my program.
I have a website that loads perfectly on various browsers on Windows Laptop, Android and Fire OS. The same site refuses to load on a Safari on an iPhone.
It is an angular application. While I see the index.html load, the angular does not load. I need to debug to figure out what is happening. I only have a Windows 10 laptop. How can I debug the website running on Safari on an iPhone from my Windows 10 laptop?
If you only have a windows laptop, you will need an online service like browserstack. There is no way around this. Physical Iphones can only be debugged with Safari, running on physical Mac desktops or laptops. Browserstack is a subscription service, but it will be a lot cheaper than buying the hardware. (No affiliation)
Follow below link
Building and debugging websites and web applications for mobile devices can be a hassle. On the desktop we have powerful debugging tools; most browsers have a web inspector of some kind. But we don’t have those tools for devices like the iPhone and iPad … that is, until now!
https://webdesign.tutsplus.com/articles/quick-tip-using-web-inspector-to-debug-mobile-safari--webdesign-8787
I have Samsung device with stock browser that called Internet.
The device is over 4.4 version.
I'm trying to remote debug the stock browser on a real device without success.
Already succeeded to remote debug chrome.
Is it possible on a real device and not on emulator?
The problem is just Samsung's stock browser
Hi!, Appium started to work with Android's stock browser (named.. Browser) since v1.3, the actual problem is the Samsung stock browser isn't Browser, it's Internet! These both apps are different (shame on Samsung!, not Appium guys fault). All other Android distributions that stock browser is Browser are working fine with Appium >= v1.3 as I've said before.
Emulator stock browser is Browser, that's why it's working for you on Emulator!
Why Appium doesn't work with Samsung's stock browser?
Appium are built to work with Chromium WebView (present on Chrome and Browser) , and Internet does not have it. So it doesn't work with Appium now, and probably won't work never, as Appium's maintainers does not have any interest to do the automation outside Chromium WebView. See this issue for more information: https://github.com/appium/appium/issues/4509
Ok, but how do I use Appium with Samsung devices?
So, the only solution is installing Chrome into your samsung device.
If you can't access the store to install the Chrome app, you can download and install manually the Chrome APK into your device (or other browser that uses Chromium webview, such as Chromium and ContentShell).
PS: ContentShell is basically only Chromium webview, without favorites, bookmarks and other common browser stuff, so it's pretty good for Appium testing.
This is weird. I created a Facebook iFrame App that worked fine in every browser I've tested it on. Then Mountain Lion came out. For some reason macs running the new OS and Safari 6 can't see the app. The Facebook chrome is there, but the website isn't loading. (The app is just a website hosted elsewhere). I have another mac running lion that has Safari 6, but it works fine. So it has to be Mountain Lion that's causing this problem. I don't see how the operation system would affect this, but it seems to be.
Any suggestions?
No matter what browser I am using, the address https://www.yellow-mountain.com/latest_picture/ is not reachable (my browsers try to connect to the HTTPS version because I am browsing FB over HTTPS). And even outside any iframes I can not connect to that address.
Reaching it just via HTTP works fine though.
So talk to your server admin about getting SSL to work for your server/domain.
Try to clear the browser's cache. It works pretty well for me.
I am building a .NET website with MonoDevelop on OSX Lion that is targeted for mobile devices.
On my desktop's browser, I am able to access the site via http://127.0.0.1:8080, but I would like to view it on my physical iPhone (I don't want to use the XCode simulator).
My iPhone and Mac are on the same network and I have enabled Web Sharing. I can actually get to the default Apache index.html (http://192.168.1.104:80) page, but I am not able to get to my site (http://192.168.1.104:8080).
I'm newer to the Mac and even less familiar with network management, so I hope I'm missing something very simple.
You may as well turn off web-sharing because web-sharing only operates the built-in Apache web-server.
What is happening is that the web-server that MonoDevelop is hosting your pages on has been set up to only allow connections coming from localhost. If this is the problem, entering in the lan IP of the OS X machine on the OS X machine will likely also not work (if the IP filtering work like it does on Apache).
You need to find the config files for the MonoDevelop server and allow access from addresses other than 127.0.0.1