Current 3.6 trunk wont install

[csixty4]

Setup for a fresh WP 3.6 install using current trunk crashes with an empty white box on a gray background.

[18-Feb-2013 22:53:56] PHP Fatal error:  Call to undefined function wp_kses_normalize_entities() in /Applications/MAMP/htdocs/wp36/wp-includes/formatting.php on line 2797
[18-Feb-2013 22:53:56] PHP Stack trace:
[18-Feb-2013 22:53:56] PHP   1. {main}() /Applications/MAMP/htdocs/wp36/wp-admin/setup-config.php:0
[18-Feb-2013 22:53:56] PHP   2. setup_config_display_header() /Applications/MAMP/htdocs/wp36/wp-admin/setup-config.php:109
[18-Feb-2013 22:53:56] PHP   3. esc_url() /Applications/MAMP/htdocs/wp36/wp-admin/setup-config.php:103

Patch assuming it's ok to load kses.php at this point

Broken in [23413]. We don't include kses.php in setup-config.php:
http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/setup-config.php#L58

Should we revert to esc_attr_e() there, or perhaps include kses.php?

I think I am okay with esc_attr here.

23516.1.diff replaces esc_url() with esc_attr().

In 23455:

Revert to esc_attr_e() in setup-config.php to prevent a fatal error.
kses.php is not loaded at this point, so esc_url() cannot be used.

props csixty4, JustinSainton.
fixes #23516. see #23334.

Shouldn't it still be echo esc_attr() then, rather than using a translation function with esc_attr_e()? Or was that not part of the original ticket?

#23518 was marked as a duplicate.

Replying to obenland:

Shouldn't it still be echo esc_attr() then, rather than using a translation function with esc_attr_e()? Or was that not part of the original ticket?

The intention of #23334 was to use esc_url() where possible, while keeping the links translatable.