# Troubleshooting

For general questions about Tumult Whisk and pre-purchase questions, please visit our FAQ.

# HTML

# Why does my page not look like I expect?

Whisk's Web Preview uses WebKit, the same rendering engine found in Safari. For most purposes, the rendering should be identical to Safari. If elements are not rendering or being laid out as expected, it is recommended to check in Safari and also against other browsers using the Browser Preview feature.

# How do I debug the web page?

To debug the rendering of the Web Preview, you can use the Developer Tools to inspect DOM elements.

# JavaScript

# How do I see console output or run the JavaScript debugger?

Debugging and seeing JavaScript output can be accomplished through the Developer Tools.

# Why do my alerts and prompts not work?

Some JavaScript features that spawn dialogs like alert() and prompt() do not activate in Whisk.

# Why is my page not refreshing anymore?

If your JavaScript code has an infinite loop, the Web Preview will stop rendering. You should correct the fault, save the document, and then relaunch Whisk.

For this reason, it may be prudent to use a manual refresh when working with JavaScript code. Sometimes infinite loops can be created unintentionally in an intermediate edit.

# PHP

# Why do my server-side variables not work?

Variables like DOCUMENT_ROOT, and other $_SERVER variables are not available in Whisk's environment. Whisk executes the PHP code through the command-line, and not Apache, therefore there is no server (and no server variables). These variables can be simulated manually in an include file if necessary.

# Why did my page stop rendering?

If your PHP code has an infinite loop, the Web Preview will stop rendering. You should correct the fault, save the document, and then relaunch Whisk.

For this reason, it may be prudent to use a manual refresh when working with PHP code. Sometimes infinite loops can be created unintentionally in an intermediate edit.

# Reporting Bugs

If you notice issues operating buttons, menus, or are experiencing issues specific to Whisk, please submit a bug report. Including your document and logs will help us find a solution for you quickly and potentially resolve the bug you're reporting for everyone.

To submit a bug report, chose the Help > Report an Issue… menu item.

When you do so, please also include your document in the Issue Reporter's Attachments section, and ensure that the "Send logs, preferences, and system information" checkbox is checked.

If you don’t fill in the email field, your bug report may be helpful to us, but we won’t know how to get back to you with a potential resolution.

Whisk's Issue Reporter
Whisk's Issue Reporter

The more detail you provide, the easier we can find a fix!