Correctly handled now as Format -> Cells -> Numbers tab: "Text" category. With Sidebar -> Styles -> Text: "Hyperlink" to style.

But if ODF or extending supports it--defining a "URL" (or "URI" for other schemes--e.g. ftp, ldap, mailto, etc.) category separate from the "Text" category, and ability to Style that cell content, would offer better UX.

And should have noted that a "hyperlink", as entered currently in a cell, can already be followed with a <Ctrl>+click of the cell.

Seems like the "Open Hyperlink" should be available to assign as a shortcut in customizing Calc, but does not match the <Ctrl>+click mouse action.

Dont get the proposal. There are three ways to format hyperlinks:

a) insert http://123.com into a cell (and let the autoformat work; Tools > Autocorrect > Options > URL recognition)
b) insert hyperlink as formula (=hyperlink("http://123.com";<"123">)
c) format as hyperlink (Sidebar > Styles > Text > Hyperlink)

What exactly should be changed for which use case?

This is not only for the formatting of a cell holding a Hyperlink.

What is lacking is a dedicated Cell format for URI's--URL's being just one scheme. 

Formatting for all URI's are handled as "Text", but when entered get a Number -> General assignment as even if autoformatted their cells are not categorized as Text. I.e. select the cell after entering a URL, and Format -> Cell. With defaults now it is assigned a Number: General format.

Effort here would be to create a selectable category for the Number panel to explicitly input URI's--and to derive their style formatting from Text cell style formatting as now for the "Hyperlink" style.  Imagine we could describe cell style formatting for URLs (http, https), ftp, email, etc. based on the URI. 

A <Ctrl>+click, or Double-click, or Open Hyperlink to follow the URI held in the cell.  Establishing a specific URI category for cell content would allow us to tailor LO's behavior to the different "schemes"--if only to correctly pass them on to the os/DE

The cell style is independent from the cell content and has to be set manually (subsummizing autoformat or conditional formatting). I doubt we can automatically assign a style to a cell since styles are variable and 'Hyperlink' is not necessarily defined (although it's hard-coded). [1]
Combining the internal hyperlink formatting (gray background or green font, depending on the kind of input) has also the risk to clash with the hyperlink text style

The number format of a cell is never set automatically. You can enter 1.23$ or "Test" and all becomes a number/general by default. So before we talk about URIs wouldn't it require those formats?

Extending the number formats by a special kind of text, the hyperlink, sounds also not possible as we are restricted by the format. Plus, what would that format contain other than text (left aligned)? Do you have something like "http://@" in mind?

[1] In fact, ODF has a <number:text-style> format, http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1416346_253892949

While I read the first comments I thought this results in a mixture of content declaration and style definition. For me so far, a hyperlink was only a 'character property' of a (part of) text content in a cell.

But there may be use cases where a general declaration as cell format could be useful. So I'm with this enhancement request.

What's Regina's opinion regarding ODF specification? Adding her in CC list.

Regina, polite ping :-)

Dear Robert Domitz,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp