Works as expected on Firefox with the same device.

Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0

Steps Followed:
1. Launched the Chrome Browser.
2. Navigate to the URL:  http://output.jsbin.com/nocagos
3. Observed that “H264” component is not displayed.

However for the same Chrome version on Samsung J710 Android 7.0.0 the following value is displayed: a=rtpmap:99 rtx/90000

Chrome versions tested:
60.0.3072.0, 64.0.3282.137(Stable), 67.0.3362.0(Canary)

OS:
Android 7.1.2

Android Devices:
Nexus 9 Build/N2G47Z

This seems to be a Non-Regression issue as same behavior is seen since M60.  Untriaged for further input's on this issue.

Please navigate to below link for log's and screenshot--
go/chrome-androidlogs/818529

Note: H264 component is not displayed for FireFox mobile version.

Thanks!

magjed@ can you triage?

We have no SW fallback for H264 on Android as far as I know.

True. That's because we don't have SW H264 available on Android so far.

IMO, having it, would make interop way simpler for H264. FF has it AFAIK.

H264 software codec is included in Android starting version 6.0 (M) and this encoder has support for larger resolutions. If OMX.google.h264.encoder & OMX.google.h264.decoder were white-listed, we will significantly increase the foot-print of Android devices that support H264 and hence inter-operate with Safari. 

We haven't test it's performance for WebRTC purpose yet. I can take a look if it's a good alternative.

We have tested it with our native Android SDK and have concluded that it is a fairly good alternative on devices that do not have the whitelisted hardware H264 codecs. 

I did some quick tests again omx.google.h264. 
On latest devices and OS version, i.e. Pixel+O, it works pretty well.
On elder device and OS version, i.e. Nexus9+N, it's worse, not much though, than VP8 with same settings.

Some issues noticed:
- It won't follow out bps setting for BWE, but works with its own strategy. Need more tests with poor network connection.
- It will work in burst some time, especially at beginning.
- Possible interruption. My test app will lost connection at working with omx.google.h264 without obvious reason, while HW h264 and SW VP8 always work well. Need more investigation.

So it looks like a good alternative now, but more working is needed. I'll take a look into it later.  

Assuming this should be bumped to M69?